Tenant-aware mutual TLS authentication
The tenant-aware mTLS authentication system addresses mTLS implementation challenges by using client certificates and browser redirects for secure, efficient access to multi-tenant cloud platforms, reducing user interaction and enhancing security.
Patent Information
- Application Number
- JP2024140945
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2020-12-04
- Filing Date
- 2024-08-22
- Publication Date
- 2024-12-03
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing cloud platforms face challenges in implementing mutual Transport Layer Security (mTLS) authentication for client devices due to complexities in issuing certificates, leading to security vulnerabilities and user interaction issues in accessing multi-tenant database systems.
A tenant-aware mTLS authentication system that uses client digital certificates and mTLS services to authenticate user devices, leveraging browser redirects for minimal user interaction, ensuring secure access by validating certificate chains and issuing time-limited access tokens.
Provides secure and efficient authentication for client devices in multi-tenant systems with reduced user interaction, enhancing security by validating client certificates and minimizing unauthorized access.
Smart Images

Figure 2024167271000001_ABST
Abstract
Description
[Technical field]
[0001] [Cross reference] This application claims priority to U.S. patent application Ser. No. 17 / 112,525, entitled “TENANT AWARE MUTUAL TLS AUTHENTICATION” by Peddada et al., filed Dec. 4, 2020, which is assigned to the assignee of the present application.
[0002] [Technical field] The present disclosure relates generally to database systems and data processing, and more specifically to tenant-aware mutual Transport Layer Security (mTLS) authentication. [Background technology]
[0003] Cloud platforms (i.e., computing platforms for cloud computing) may be adopted by many users to store, manage, and process data using a shared network of remote servers. Users may develop applications on the cloud platform to handle the storage, management, and processing of data. In some cases, the cloud platform may utilize a multi-tenant database system. Users may access the cloud platform using a variety of user devices (e.g., desktop computers, laptops, smartphones, tablets, or other computing systems, etc.).
[0004] In one example, the cloud platform may support a customer relationship management (CRM) solution, which may include support for sales, service, marketing, communities, analytics, applications, and the Internet of Things. A user may utilize the cloud platform to help manage the user's contacts. For example, managing the user's contacts may include analyzing data, storing and preparing communications, and tracking opportunities and sales.
[0005] A variety of cryptographic protocols and techniques may support authentication to a variety of systems. These techniques may support privacy and data integrity. In some cases, these techniques use digital certificates that support a chain of trust between certificate issuers and the parties that own those certificates. [Brief description of the drawings]
[0006] [Figure 1] 1 illustrates an example system for providing access to services that support tenant-aware mutual Transport Layer Security (mTLS) authentication, according to an aspect of the present disclosure. [Diagram 2] 1 illustrates an example of a system that supports tenant-aware mTLS authentication, according to an embodiment of the present disclosure. [Diagram 3] 1 illustrates an example of a system that supports tenant-aware mTLS authentication, according to an embodiment of the present disclosure. [Figure 4] 1 illustrates a process flow for supporting tenant-aware mTLS authentication, according to an embodiment of the present disclosure. [Diagram 5] FIG. 1 illustrates a block diagram of an apparatus that supports tenant-aware mTLS authentication, according to an embodiment of the present disclosure. [Figure 6] 1 illustrates a block diagram of a security manager that supports tenant-aware mTLS authentication in accordance with an embodiment of the present disclosure. [Figure 7] FIG. 1 illustrates a diagram of a system including a device that supports tenant-aware mTLS authentication, according to an embodiment of the present disclosure. [Figure 8] FIG. 1 illustrates a block diagram of an apparatus that supports tenant-aware mTLS authentication, according to an embodiment of the present disclosure. [Figure 9] 1 illustrates a block diagram of a security manager that supports tenant-aware mTLS authentication in accordance with an embodiment of the present disclosure. [Figure 10] FIG. 1 illustrates a diagram of a system including a device that supports tenant-aware mTLS authentication, according to an embodiment of the present disclosure. [Figure 11] 1 shows a flowchart illustrating a method for supporting tenant-aware mTLS authentication according to an aspect of the present disclosure. [Figure 12] 1 shows a flowchart illustrating a method for supporting tenant-aware mTLS authentication according to an aspect of the present disclosure. [Figure 13] 1 shows a flowchart illustrating a method for supporting tenant-aware mTLS authentication according to an aspect of the present disclosure. [Figure 14] 1 shows a flowchart illustrating a method for supporting tenant-aware mTLS authentication according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0007] Various systems, services, data, and combinations thereof are secured using various techniques. In some examples, a user may enter a username and / or password to gain access to these secured systems. In the same or alternative examples, various cryptographic protocols and techniques may be used to gain access to these systems. Transport Layer Security (TLS) is a cryptographic protocol that may be used to provide secure access to systems such as application servers. This protocol is used to provide privacy and data integrity. In such systems, a server may provide a digital certificate to a client, which may indicate, among other characteristics, the server's public key and the certificate authority that vouches for the certificate. In mutual TLS (mTLS) systems, both the server and the client may exchange certificates. However, such systems are not widely used in server-client scenarios where the client is an actual user device (e.g., rather than server-to-server communication). mTLS may not be used because issuing certificates to client devices can be complicated.
[0008] The techniques described herein support the use of mTLS services trusted by or otherwise associated with a tenant of a multi-tenant system to access services supported by the tenant, such as a data access service, an application server, an analytics server, or a data store. A client, which may be an example of a user device (e.g., a browser), may be configured with a certificate associated with the tenant. For example, the certificate may be issued or provisioned by the tenant using a certificate authority supported by the tenant or using a certificate authority trusted by the tenant. The client may request access to a tenant service, and the tenant service may determine whether the client possesses a valid access indicia, which may be an example of a browser cookie, a JavaScript Object Notation (JSON) Web token, a Hypertext Transfer Protocol (HTTP) parameter, or a combination thereof. The access indicia may be issued to the client by the service and may be associated with a time to live value. Thus, if the time to live value has expired, the service may determine that the access indicia is invalid.
[0009] If the service determines that the client does not possess a valid access indicia, the service may send a redirection response to the client, which may indicate an endpoint of an mTLS service associated with or trusted by the tenant. In response to receiving the redirection response, the client may perform a digital handshake with the mTLS service, which may validate the client digital certificate and digitally sign the client digital certificate using a private key associated with the mTLS service. Signing the digital certificate may establish a chain of trust between the client and the mTLS. The mTLS may send a redirection response redirecting the client to a service to which the client presents an indication of the digitally signed digital certificate chain. The service may validate the trust chain associated with the digitally signed digital certificate chain and issue an indication that the client is authorized to access the service. The indication may be an example of an access indicia (e.g., a browser cookie, a JSON web token, an HTTP parameter) that the client may use for a period of time defined by a time-to-live value associated with the access indicia.
[0010] Thus, according to these and other techniques described herein, a client may use a client digital certificate and an mTLS service to access a service supported by a tenant of a multi-tenant system. Because the service trusts mTLS, the service may trust that mTLS has validated the client certificate. Furthermore, because these techniques may be implemented using browser redirection, various validation and authentication techniques may be performed with little or no user interaction.
[0011] Aspects of the present disclosure are first described in the context of an environment supporting on-demand database services. Aspects of the present disclosure are further described with respect to system diagrams illustrating various signaling and process flows supporting tenant-aware mTLS authentication. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow charts relating to tenant-aware mTLS authentication.
[0012] FIG. 1 illustrates an example of a system 100 for cloud computing supporting tenant-aware mTLS authentication according to various aspects of the disclosure. The system 100 includes a cloud client 105, a contact 110, a cloud platform 115, and a data center 120. The cloud platform 115 may be an example of a public or private cloud network. The cloud client 105 may access the cloud platform 115 through a network connection 135. The network may implement Transmission Control Protocol and Internet Protocol (TCP / IP), such as the Internet, or may implement other network protocols. The cloud client 105 may be an example of a user device, such as a server (e.g., cloud client 105-a), a smartphone (e.g., cloud client 105-b), or a laptop (e.g., cloud client 105-c). In other examples, the cloud client 105 may be a desktop computer, a tablet, a sensor, or another computing device or system capable of generating, analyzing, transmitting, or receiving communications. In some examples, the cloud client 105 may be operated by a user that is part of a corporation, a business, a non-profit, a startup, or any other type of organization.
[0013] A cloud client 105 may interact with multiple contacts 110. An interaction 130 may include a communication, an opportunity, a purchase, a sale, or any other interaction between a cloud client 105 and a contact 110. Data may be associated with the interaction 130. The cloud client 105 may access the cloud platform 115 to store, manage, and process the data associated with the interaction 130. In some cases, the cloud client 105 may have an associated security or permission level. Based on the associated security or permission level, the cloud client 105 may access certain applications, data, and database information within the cloud platform 115 but not others.
[0014] Contacts 110 may interact with cloud client 105 directly or via telephone, email, web, text message, mail, or any other suitable form of interaction (e.g., interactions 130-a, 130-b, 130-c, 130-d). Interactions 130 may be business-to-business (B2B) interactions or business-to-consumer (B2C) interactions. Contacts 110 may also be referred to as customers, potential customers, leads, clients, or any other suitable terminology. In some cases, contacts 110 may be examples of user devices, such as a server (e.g., contact 110-a), a laptop (e.g., contact 110-b), a smartphone (e.g., contact 110-c), or a sensor (e.g., contact 110-d). In other cases, contacts 110 may be another computing system. In some cases, contacts 110 may be operated by a user or a group of users. A user or a group of users may be associated with a company, a manufacturer, or any other suitable organization.
[0015] The cloud platform 115 may provide on-demand database services to the cloud clients 105. In some cases, the cloud platform 115 may be an example of a multi-tenant database system. In this case, the cloud platform 115 may serve multiple cloud clients 105 with a single instance of software. However, other types of systems may be implemented, including, but not limited to, client-server systems, mobile device systems, and mobile network systems. In some cases, the cloud platform 115 may support CRM solutions. This may include support for sales, service, marketing, communities, analytics, applications, and the Internet of Things. The cloud platform 115 may receive data associated with contact interactions 130 from the cloud clients 105 via a network connection 135 and may store and analyze the data. In some cases, the cloud platform 115 may receive data directly from interactions 130 between the contacts 110 and the cloud clients 105. In some cases, the cloud clients 105 may develop applications to run on the cloud platform 115. The cloud platform 115 may be implemented using remote servers. In some cases, the remote servers may be located in one or more data centers 120.
[0016] Data center 120 may include multiple servers. Multiple servers may be used for data storage, management, and processing. Data center 120 may receive data from cloud platform 115 via connection 140, or directly from cloud clients 105, or from interactions 130 between contacts 110 and cloud clients 105. Data center 120 may utilize multiple redundancies for security purposes. In some cases, data stored in data center 120 may be backed up by copies of the data in a different data center (not shown).
[0017] Subsystem 125 may include cloud client 105, cloud platform 115, and data center 120. In some cases, data processing may occur in any of the components of subsystem 125 or in a combination of these components. In some cases, a server may perform data processing. The server may be cloud client 105 or may be located in data center 120.
[0018] In some cases, cloud platform 115 may support client authentication prior to providing access to services supported by cloud platform 115. For example, cloud platform 115 and associated systems may support services such as application servers, data access, or other types of services to various users, such as employees of cloud client 105. More specifically, cloud client 105 may configure one or more services in cloud platform 115, and employees, users, customers, etc. of cloud client 105 may access services supported by cloud platform 115. For example, various client authentication techniques, such as username and password, TLS authentication, among others, may be used to support access to the services.
[0019] As described, some services may support client authentication using a username and password. However, such systems may be subject to user error or other problems that may result in unauthorized access to the system or inability of a user to access the system. Thus, a system that supports client authentication with little or no user interaction may be more secure.
[0020] Implementations described herein may leverage client digital certificates, mTLS services associated with tenants, and access indicia to support authentication to services supported by tenants of the cloud platform 115. For example, the cloud platform 115 may support mTLS services that are used and trusted by various tenants of a multi-tenant system supported by the cloud platform. A client (e.g., a cloud client 105 device) may request access to a service associated with a tenant and supported by the cloud platform 115. To authenticate to a service, the service may determine whether the client has a valid access token / indicia (e.g., a JavaScript object notation (JSON) web token) before granting access. If the client does not have a valid access token, the client may be redirected to an mTLS service supported by the cloud platform that authenticates the client's digital certificate. Based on authentication of the certificate by mTLS, the client may receive a new valid access token and use this token to access the service for a period of time. This process supports secure and efficient authentication because mTLS may use the server's (e.g., mTLS service's) and client's certificates. Furthermore, because browser redirection may be used, little or no user interaction may be required, which may avoid or limit unauthorized access or locking out users from the service.
[0021] It should be understood by those skilled in the art that one or more aspects of the present disclosure may additionally or alternatively be implemented in the system 100 to solve problems other than those described herein. Furthermore, aspects of the present disclosure may provide technical improvements over the "conventional" systems or processes described herein. However, the description and accompanying drawings only include exemplary technical improvements resulting from implementing aspects of the present disclosure, and therefore do not necessarily represent all of the technical improvements provided within the scope of the claims.
[0022] In an exemplary utilization of the techniques described herein, the client may be an example of a browser used by an employee of the cloud client 105. The browser or the device running the browser may store and access a digital certificate. For example, a private key associated with the digital certificate may be stored in the client's secure enclave. The digital certificate and private key may be provisioned by a tenant (e.g., the cloud client 105) or a certificate authority associated with the tenant. The client / browser may request access to a service supported by the cloud client 105. For example, a user may navigate to a uniform resource locator (URL) associated with the service. The service may determine whether the client has been provisioned with an access indicia (e.g., a web browser cookie) before allowing the client to access the service. In some cases, the service determines whether a time to live associated with the cookie is valid or expired. If the service determines that the client does not have a valid access indicia (e.g., no token or an expired token), the service sends a redirection response to the client, redirecting the client to an mTLS service trusted by the service and the cloud client 105. The mTLS service validates the client digital certificate (e.g., a certificate chain), signs the digital certificate, and redirects the client to the service. The service validates the certificate signed by the mTLS service and provisions the client with an access indicia (e.g., a web browser cookie) that enables the client to access the service. The provisioned access indicia may be associated with an expiration date.
[0023] FIG. 2 illustrates an example of a system 200 supporting tenant-aware mTLS authentication according to an aspect of the disclosure. The system 200 includes a user device 205, a server 210, and a server 215. The user device 205 may be an example of a laptop, desktop, tablet, smartphone, or another type of user computing system. The user device 205 executes a client 220, which may be an example of a client application, such as a browser, or other application executing on the user device 205. The server 210 and / or the server 215 may be examples of the cloud platform aspect of FIG. 1. For example, the server 210 may be an example of an application server or a web server. The server 210 may host various services, such as web application services or one or more websites. The server 215 may host an mTLS service. In some examples, the servers 210 and 215 are hosted in the same physical or logical system or in separate systems. The client 220 may be provisioned with or have access to a client digital certificate (e.g., a certificate chain) associated with a private key.
[0024] The client 220 may send an access request 225 to the server 210. The access request may be an example of an HTTP request, an application programming interface (API) request, etc. In some examples, the access request 225 is sent to the server 210 in response to a user navigating to a website URL, activating a service on an application, etc. In response to receiving the access request, the service (e.g., the server 210) may determine whether the client 220 has been provisioned with a valid access indicia. The access indicia may be an example of a web browser cookie, a JSON web token (JWT), etc. More specifically, the access indicia may include, for example, a payload making an assertion that the client 220 is authorized to access a service supported by the server 210. In some examples, the access indicia is digitally (e.g., cryptographically) signed using a key, such as a key associated with the server 210. Thus, the server may have pre-provisioned the client 220 with a signed access indicia. In some cases, the access indicia includes an expiration date or another field indicating when the indicia will expire. Thus, upon receiving a request, server 210 may determine whether the access indicia is valid based on the expiration date and based on the digital signature. If the server determines that client 220 possesses a valid access indicia, server 210 may grant access to the service.
[0025] If the server 210 determines that the client 220 does not possess a valid access indicia (e.g., the token has expired, the server 210 cannot validate the signature, or the client 220 does not possess the access indicia), the server 210 may send a redirection response 230 to the client. The redirection response 230 may be in the form of a browser redirect. The redirection response 230 may indicate the mTLS services supported by the server 215. Thus, in response to receiving the redirection response 230, the client 220 may navigate to the mTLS service (e.g., send an HTTP request to the mTLS service).
[0026] The mTLS service of the server 215 performs mutual authentication with the client 220 using the mutual entity authentication principle. More specifically, the client 220 and the mTLS service may verify the identity of the other using a digital handshake 235. As part of the digital handshake procedure, the client 220 may request a valid certificate from the server 210 and validate the certificate. Furthermore, the server 215 may request a valid certificate from the client 220 and validate the certificate. The validation of the certificate may include exchanging an encrypted random challenge and proving that the certificate is valid by decrypting the random challenge with a private key associated with the certificate. For example, to validate a server certificate, the client 220 may encrypt a random challenge using the public key of the server certificate. The server may then prove the validity of the certificate by decrypting the random challenge with a private key associated with the certificate. Similarly, the server 215 may validate the client digital certificate. The handshake may also include validating the trust chain of the certificate. Although aspects of the present disclosure are described with respect to mTLS, it should be understood that other cryptographic protocols in which both parties exchange certificates may be used within the context of the present disclosure.
[0027] During mutual authentication, the mTLS service may digitally sign the client certificate (e.g., client certificate chain) and associate an expiration date with the signed certificate chain. The client certificate may be an example of an X.509 certificate. This payload (e.g., client certificate chain and expiration date) may be provided to the client as an access indicia, such as a JWT as described herein. Additionally, the client 220 may be redirected to the service via a redirection response from an mTLS service supported by the server 215. The client 220 presents the signed certificate chain 240 to the service supported by the server 210. In some cases, the service is configured to access the access indicia (e.g., signed certificate chain 240) stored at the client 220 (e.g., as a browser cookie). Thus, the client "presenting" the signed certificate chain 240 may include the client sending a request and the service accessing the cookie. The service may validate the access indicia by determining that the expiration date has not passed and by validating the signature based on the mTLS public key. If the service validates the access indicia, the service may generate a new short-lived access indicia 245 associated with the service and provide the access indicia 245 to the client 220 (e.g., store a web browser cookie). This access indicia 245 may support access to the service for a period of time defined by an expiration or time-to-live value.
[0028] Thus, according to these techniques, services supported by server 210 and mTLS services supported by server 215 may implement certificate validation, and therefore client authentication, along with browser redirection to authenticate the client. Moreover, according to these techniques, client 220 may be validated with little or no interaction by the user of user device 205. Furthermore, the use of mTLS with client certificates may provide an additional layer of security compared to other authentication techniques, without introducing vulnerabilities into username and password based systems.
[0029] FIG. 3 illustrates an example of a system 300 supporting tenant-aware mTLS authentication according to an aspect of the disclosure. System 300 includes server 210 and server 215, which may be examples of the corresponding devices described with respect to FIG. 2. For example, server 210 may support services (e.g., applications, websites, or other computing services) associated with tenants of a multi-tenant system. For example, the services may be examples of tenant websites or web applications. Server 215 may support mTLS services that may be used to authenticate to services of various tenants of the multi-tenant system, such as the services supported by server 210. The flow illustrated in FIG. 3 may be performed by server 210 and server 215 and associated with a client (e.g., client 220 of FIG. 2).
[0030] At 305, a user of the client may navigate the client to a service supported by server 210 and protected by an mTLS service supported by server 215. At 310, server 210 may determine whether the client possesses a valid access indicia. For example, server 210 may determine whether the access indicia is valid, signed by the service, has not expired (e.g., based on an expiration or time-to-live value), or a combination thereof. If the client possesses a valid access indicia, server 210 may allow the client to access the service, at 360. If the client does not possess a valid access indicia, server 210 may send a redirection response to the client, which may indicate an mTLS service supported by server 215.
[0031] The redirection response may cause the client to send a request (e.g., an HTTP request) to an mTLS service supported by server 215. In response to receiving the request, the mTLS service may perform a digital handshake with the mTLS service, at 320, which may include exchanging and validating certificates, among other processes. The mTLS service may determine, at 320, whether the mTLS digital handshake was successful or unsuccessful. If the mTLS digital handshake fails (e.g., the mTLS service cannot validate the client certificate chain), the mTLS service may deny access, at 365. In some examples, the access denial may include redirecting the client to a denial page. If the mTLS is successful, the mTLS service may digitally sign the client certificate chain, at 330, and generate and associate an expiration date with the signed certificate chain. A payload including the signed certificate chain and the expiration date may be provided to the client as an access indicia (e.g., a web browser cookie). Additionally, the mTLS service may send a redirection response to the client, which may indicate the service. In some cases, the redirection response includes a payload that includes a signed certificate chain and an expiration date.
[0032] An expiration time is associated with the signed client certificate chain to avoid replay attacks. Thus, the expiration time is used to validate that the signed payload is fresh or was generated in a recent period of time. In some examples, the expiration time is on the order of 5-15 minutes. Thus, the mTLS service signs the payload (including the certificate chain and / or the expiration time) to generate a digital signature that the service can later verify (e.g., using the mTLS public key). In some cases, if the client is configured with multiple certificates, the browser may trigger a user interface (UI) for the user to select the certificate to use for mTLS authentication. Thus, the client may receive a selection of certificates to be presented to mTLS.
[0033] In response to receiving the redirection response from the mTLS service, the client may send another access request (e.g., an HTTP request) to the service at 340. In response, the service determines whether the client possesses a valid access indicia, which may be a payload including a client certificate chain signed by the mTLS server and an associated expiration date. Thus, determining whether the client has a valid access indicia may include determining whether the expiration date has expired. If the service determines that the client does not possess a valid access indicia, the server may deny access to the service at 370. If the access indicia is valid, the service may determine at 345 whether the certificate is valid. This process may include validating a trust chain associated with the certificate. For example, the service may determine that the client certificate chain is signed by the mTLS private key. In some examples, validating the trust chain may include verifying the client certificate chain with a root that the tenant trusts. In an example of a multi-tenant system where each tenant may use the mTLS service for authentication, each tenant or a subset of tenants may use the same root. More specifically, each tenant may trust the same root and therefore validate their respective client certificate chains using this root, and if the certificate chain is not validated, the service may deny access to the client.
[0034] If the certificate chain is validated at 345, the service may generate another access indicia at 350 to be assigned to the client. The access indicia may allow the client to access the service at 355. The access indicia generated at 350 may be associated with a lifetime that is longer than the lifetime associated with the signed client certificate chain. For example, the access indicia may be associated with an expiration date that is a few hours to a day after the access indicia is generated. The length of the expiration date may be based on, for example, tenant configuration. Thus, some tenants may configure a shorter expiration date for higher security. Once the expiration date expires, the client 220 may perform another mTLS authentication to authenticate to the service.
[0035] 4 illustrates an example process flow diagram 400 for supporting tenant-aware mTLS authentication according to an aspect of the disclosure. The process flow diagram includes a server client 220, a server 210, and a server 215, which may be examples of the corresponding devices described with respect to FIGs. 2 and 3. The client 220 may be an application executable on a user device, such as the user device 205 of FIG.
[0036] At 405, the server 210 and services supported by tenants of the multi-tenant system may receive an access request from a client 220 to access a service. The client 220 may be configured with a digital certificate chain associated with the tenant. The digital certificate chain may be associated with the tenant based at least in part on being issued or provisioned by the tenant using a third-party certificate authority. The request may be sent by the client based at least in part on the client 220 being navigated to an endpoint (e.g., a URL, an API endpoint) by a user of the client 220. For example, the request may be an example of an HTTP request.
[0037] At 410, a service supported by server 210 may determine whether client 220 possesses a valid access indicia. For example, server 210 may determine whether an existing access indicia has expired, whether it has been signed by a signing key (e.g., the service's public key), or whether client 220 possesses an access indicia. An access indicia may be an example of a JWT, a web browser cookie, an HTTP parameter, etc.
[0038] At 415, the service supported by server 210 may send a first redirection response to client 220 indicating mutual transport layer security services supported by server 215 based at least in part on failure to receive a valid indication that the client is authorized to access the service. Thus, in response to failing to determine that client 220 possesses valid access indicia, server 210 sends a redirection response to client 220. The redirection response may be an example of an HTTP redirect, a browser redirect, or the like.
[0039] At 420, the client 220 may send a request to an mTLS service supported by the server 215. The request may be sent in response to receiving a redirection response from the server 210.
[0040] At 425, the client 220 performs a digital handshake with the mTLS service based at least in part on receiving the first redirection response. Performing the digital handshake may include, among other steps, sending an indication of a client digital certificate chain associated with the mutual transport layer security service.
[0041] At 430, the client 220 may receive a second redirection response from the mTLS service including a digitally signed version of the client digital certificate chain based at least in part on the digital handshake. The digital certificate chain is signed using a private key associated with the mutual transport layer security service. The redirection response with the signed digital certificate chain may be sent by the server 215 based at least in part on validating the client's digital certificate chain. The mTLS service may be configured to support multiple tenants of a multi-tenant system for authenticating different clients to different services.
[0042] At 435, the service supported by server 210 may receive from client 220 an indication of a digitally signed version of the digital certificate chain. The client may present an indication of the digitally signed version of the digital certificate chain based at least in part on receiving the second redirection response. The indication of the digitally signed version of the client digital certificate chain may be presented by client 220 based at least in part on an access request (e.g., an HTTP request) sent to the service in response to the redirection response.
[0043] At 440, a service supported by server 210 may validate the digitally signed version of the digital certificate chain. Validation may include determining that the signed certificate chain has not expired, validating the trust chain (e.g., that the chain is signed by an mTLS signing key), among other procedures. At 445, server 210 may send an indication to client 220 that the client is authorized to access the service based at least in part on validating the digitally signed version of the digital certificate chain. The indication may be an instance of an access indicia (e.g., a JWT) that asserts that the client can access the service. In some examples, the access indicia is associated with an expiration date.
[0044] 5 illustrates a block diagram 500 of an apparatus 505 supporting tenant-aware mTLS authentication according to an aspect of the disclosure. The apparatus 505 may include an input module 510, a security manager 515, and an output module 545. The apparatus 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses). In some cases, the apparatus 505 may be an example of a user terminal, a database server, or a system including multiple computing devices.
[0045] The input module 510 may manage input signals for the device 505. For example, the input module 510 may identify input signals based on interactions with a modem, keyboard, mouse, touch screen, or similar device. These input signals may be associated with user input or processing in other components or devices. In some cases, the input module 510 may utilize an operating system, such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system, to process the input signals. The input module 510 may send aspects of these input signals to other components of the device 505 for processing. For example, the input module 510 may send input signals to a security manager 515 to support mTLS authentication. In some cases, the input module 510 may be a component of an input / output (I / O) controller 715, which is described with reference to FIG. 7.
[0046] Security manager 515 may include an access request interface 520, an access component 525, a certificate chain component 530, a certificate validation component 535, and an authentication component 540. Security manager 515 may be an example of an aspect of security manager 605 or 710 described with reference to Figures 6 and 7.
[0047] The security manager 515 and / or at least some of its various subcomponents may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions of the security manager 515 and / or at least some of its various subcomponents may be performed by a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure. The security manager 515 and / or at least some of its various subcomponents may be physically located in various locations, including being distributed such that portions of the functions are implemented by one or more physical devices at different physical locations. In some examples, the security manager 515 and / or at least some of its various subcomponents may be separate and distinct components according to various aspects of the disclosure. In other examples, security manager 515 and / or at least some of its various subcomponents may be combined with one or more other hardware components, including, but not limited to, an I / O component, a transceiver, a network server, another computing device, one or more other components described in this disclosure, or combinations thereof, in accordance with various aspects of the disclosure.
[0048] The access request interface 520 may receive an access request from a client to access a service by a service supported by a tenant of the multi-tenant system, the client being configured with a digital certificate chain associated with the tenant.
[0049] The access component 525 may send a first redirection response to the client indicating the mutual transport layer security service based on failing to receive a valid indication by the service that the client is authorized to access the service.
[0050] The certificate chain component 530 may receive an indication of a digitally signed version of a digital certificate chain from a client, the digital certificate chain being signed using a root key associated with a mutual transport layer security service trusted by the truest.
[0051] The certificate validation component 535 can validate a digitally signed version of the digital certificate chain.
[0052] The authentication component 540 may send an indication to the client that the client is authenticated to access the service based on validating the digitally signed version of the digital certificate chain.
[0053] The output module 545 may manage output signals for the apparatus 505. For example, the output module 545 may receive signals from other components of the apparatus 505, such as the data persistence module 515, and may transmit these signals to other components or devices. In some particular examples, the output module 545 may transmit the output signals for display in a user interface, for storage in a database or data store, for further processing on a server or server cluster, or for any other process in any number of devices or systems. In some cases, the output module 545 may be a component of an I / O controller 715, which is described with reference to FIG. 7.
[0054] 6 illustrates a block diagram 600 of a security manager 605 supporting tenant-aware mTLS authentication according to an aspect of the disclosure. The security manager 605 may be an example of an aspect of the security manager 515 or security manager 710 described herein. The security manager 605 may include an access request interface 610, an access component 615, a certificate chain component 620, a certificate validation component 625, an authentication component 630, and an access validation component 635. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).
[0055] The access request interface 610 may receive an access request from a client to access a service by a service supported by a tenant of the multi-tenant system, the client being configured with a digital certificate chain associated with the tenant.
[0056] The access component 615 may send a first redirection response to the client indicating the mutual transport layer security service based on failing to receive a valid indication by the service that the client is authorized to access the service.
[0057] The certificate chain component 620 may receive an indication of a digitally signed version of a digital certificate chain from the client, the digital certificate chain being signed using a root key associated with a mutual transport layer security service that is trusted by the most authentic.
[0058] In some cases, the client digital certificate chain is associated with a tenant based on the client digital certificate chain being issued or provisioned by a third-party certificate authority.
[0059] The certificate validation component 625 can validate a digitally signed version of a digital certificate chain.
[0060] In some examples, the certificate validation component 625 may validate a certificate chain associated with a digitally signed version of the digital certificate chain.
[0061] In some examples, the certificate validation component 625 may determine that the expiration date associated with the digital certificate chain has not expired.
[0062] In some cases, the service is supported by a tenant of a multi-tenant system that is associated with mutual transport layer security services.
[0063] The authentication component 630 may send an indication to the client that the client is authenticated to access the service based on validating the digitally signed version of the digital certificate chain.
[0064] In some examples, the access indicia is stored at the client, and the access indicia includes a browser cookie, a JSON web token, an HTTP parameter, or a combination thereof.
[0065] The access validation component 635 may determine, based on receiving the access request, that the access indicia presented by the client is invalid, and the service sends a first redirection response based on determining that the access indicia is invalid.
[0066] In some examples, the access validation component 635 may determine that a time-to-live value associated with the access indicia has not expired.
[0067] In some cases, the access indicia includes a browser cookie, a JSON web token, an HTTP parameter, or a combination thereof.
[0068] 7 illustrates a diagram of a system 700 including a device 705 supporting tenant-aware mTLS authentication according to an aspect of the disclosure. The device 705 may be or include an example of components of an application server or apparatus 505 described herein. The device 705 may include components for bidirectional data communication, including components for sending and receiving communications, including a security manager 710, an I / O controller 715, a database controller 720, a memory 725, a processor 730, and a database 735. These components may be in electronic communication via one or more buses (e.g., bus 740).
[0069] Security manager 710 may be an example of security manager 515 or 605 described herein. For example, security manager 710 may perform any of the methods or processes described herein with reference to Figures 5 and 6. In some cases, security manager 710 may be implemented in hardware, software executed by a processor, firmware, or any combination thereof.
[0070] The I / O controller 715 may manage input signals 745 and output signals 750 for the device 705. The I / O controller 715 may also manage peripherals that are not integrated into the device 705. In some cases, the I / O controller 715 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 715 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In other cases, the I / O controller 715 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 715 may be implemented as part of a processor. In some cases, a user may interact with the device 705 through the I / O controller 715 or through hardware components controlled by the I / O controller 715.
[0071] The database controller 720 may manage data storage and processing in the database 735. In some cases, a user may interact with the database controller 720. In other cases, the database controller 720 may operate automatically without user interaction. The database 735 may be an example of a single database, a distributed database, multiple distributed databases, a data store, a data lake, or an emergency backup database.
[0072] Memory 725 may include random access memory (RAM) and read only memory (ROM). Memory 725 may store computer-readable, computer-executable software that includes instructions that, when executed, cause the processor to perform various functions described herein. In some cases, memory 725 may include a basic input / output system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.
[0073] Processor 730 may include intelligent hardware devices (e.g., a general purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 730 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 730. Processor 730 may be configured to execute computer-readable instructions stored in memory 725 to perform various functions (e.g., functions or tasks supporting tenant-aware mTLS authentication).
[0074] 8 illustrates a block diagram 800 of an apparatus 805 supporting tenant-aware mTLS authentication according to an aspect of the disclosure. The apparatus 805 may include an input module 810, a security manager 815, and an output module 845. The apparatus 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses). In some cases, the apparatus 805 may be an example of a user terminal, a database server, or a system including multiple computing devices.
[0075] The input module 810 may manage input signals for the device 805. For example, the input module 810 may identify input signals based on interactions with a modem, keyboard, mouse, touch screen, or similar device. These input signals may be associated with user input or processing in other components or devices. In some cases, the input module 810 may utilize an operating system, such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system, to process the input signals. The input module 810 may send aspects of these input signals to other components of the device 805 for processing. For example, the input module 810 may send input signals to a security manager 815 to support tenant-aware mTLS authentication. In some cases, the input module 810 may be a component of an input / output (I / O) controller 1015, described with reference to FIG. 10.
[0076] The security manager 815 may include an access component 820, a redirection component 825, an mTLS component 830, a certificate chain component 835, and an authentication component 840. The security manager 815 may be an example of an aspect of the security manager 905 or 1010 described with reference to Figures 9 and 10.
[0077] The security manager 815 and / or at least some of its various subcomponents may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions of the security manager 815 and / or at least some of its various subcomponents may be performed by a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure. The security manager 815 and / or at least some of its various subcomponents may be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations by one or more physical devices. In some examples, the security manager 815 and / or at least some of its various subcomponents may be separate and distinct components according to various aspects of the disclosure. In other examples, security manager 815 and / or at least some of its various subcomponents may be combined with one or more other hardware components, including, but not limited to, an I / O component, a transceiver, a network server, another computing device, one or more other components described in this disclosure, or combinations thereof, in accordance with various aspects of the disclosure.
[0078] The access component 820 can send an access request for accessing a service to a service supported by a tenant by a client, the client being configured with a client digital certificate chain associated with the tenant.
[0079] The redirection component 825 may receive a first redirection response from the service indicating the mutual transport layer security service based on the client's failure to present a valid indication that the client is authorized to access the service, and receive a second redirection response from the mutual transport layer security service based on a digital handshake, the second redirection response including a digitally signed version of the client digital certificate chain, the digital certificate chain being signed using a private key associated with the mutual transport layer security service.
[0080] The mTLS component 830 may perform a digital handshake with the mutual transport layer security service based on receiving the first redirection response, where performing the digital handshake includes sending an indication of a client digital certificate chain associated with the mutual transport layer security service.
[0081] The certificate chain component 835 may present, based on receipt by the client of the second redirection response, an indication of a digitally signed version of the client digital certificate chain.
[0082] The authentication component 840 may receive an indication from the service that the client is authorized to access the service based on presenting an indication of a digitally signed version of the client digital certificate chain.
[0083] The output module 845 may manage output signals for the device 805. For example, the output module 845 may receive signals from other components of the device 805, such as the security manager 815, and may transmit these signals to other components or devices. In some particular examples, the output module 845 may transmit the output signals for display in a user interface, for storage in a database or data store, for further processing on a server or server cluster, or for any other process in any number of devices or systems. In some cases, the output module 845 may be a component of an I / O controller 1015, which is described with reference to FIG. 10.
[0084] 9 illustrates a block diagram 900 of a security manager 905 supporting tenant-aware mTLS authentication according to an aspect of the disclosure. The security manager 905 may be an example of an aspect of the security manager 815 or security manager 1010 described herein. The security manager 905 may include an access component 910, a redirection component 915, an mTLS component 920, a certificate chain component 925, an authentication component 930, and a user interface component 935. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).
[0085] The access component 910 can send an access request for accessing a service to a service supported by a tenant by a client, the client being configured with a client digital certificate chain associated with the tenant.
[0086] In some examples, the access component 910 may present an access indicia by a client, and the client receives a first redirection response based on the access indicia being invalid.
[0087] In some cases, the access indicium is invalid based on the time-to-live value having expired.
[0088] The redirection component 915 may receive a first redirection response from the service indicating the mutual transport layer security service based on the client's failure to present a valid indication that the client is authorized to access the service.
[0089] In some examples, the redirection component 915 may receive a second redirection response from the mutual transport layer security service based on the digital handshake, the second redirection response including a digitally signed version of the client digital certificate chain, the digital certificate chain being signed using a private key associated with the mutual transport layer security service.
[0090] The mTLS component 920 may perform a digital handshake with the mutual transport layer security service based on receiving the first redirection response, where performing the digital handshake includes sending an indication of a client digital certificate chain associated with the mutual transport layer security service.
[0091] The certificate chain component 925 may present, based on receipt by the client of the second redirection response, an indication of a digitally signed version of the client digital certificate chain.
[0092] In some cases, the client digital certificate chain is associated with a tenant based on the client digital certificate chain being issued or provisioned by a third-party certificate authority.
[0093] The authentication component 930 may receive an indication from the service that the client is authenticated to access the service based on presenting an indication of a digitally signed version of the client digital certificate chain.
[0094] In some examples, an access indicium is received from the service, where the access indicium includes a browser cookie, a JSON web token, an HTTP parameter, or a combination thereof.
[0095] The user interface component 935 can receive from the user a selection of a client digital certificate chain issued or provisioned by the tenant, and a digital handshake is performed based on receiving the selection of the digital certificate chain.
[0096] 10 illustrates a diagram of a system 1000 including a device 1005 supporting tenant-aware mTLS authentication according to an aspect of the disclosure. The device 1005 may be or include examples of components of a user device or apparatus 805 described herein. The device 1005 may include components for bidirectional data communication, including components for sending and receiving communications, including a security manager 1010, an I / O controller 1015, a database controller 1020, a memory 1025, a processor 1030, and a database 1035. These components may be in electronic communication via one or more buses (e.g., bus 1040).
[0097] Security manager 1010 may be an example of security manager 815 or 905 described herein. For example, security manager 1010 may perform any of the methods or processes described herein with reference to Figures 8 and 9. In some cases, security manager 1010 may be implemented in hardware, software executed by a processor, firmware, or any combination thereof.
[0098] The I / O controller 1015 may manage input signals 1045 and output signals 1050 for the device 1005. The I / O controller 1015 may also manage peripherals that are not integrated into the device 1005. In some cases, the I / O controller 1015 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 1015 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In other cases, the I / O controller 1015 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 1015 may be implemented as part of a processor. In some cases, a user may interact with the device 1005 through the I / O controller 1015 or through hardware components controlled by the I / O controller 1015.
[0099] The database controller 1020 may manage data storage and processing in the database 1035. In some cases, a user may interact with the database controller 1020. In other cases, the database controller 1020 may operate automatically without user interaction. The database 1035 may be an example of a single database, a distributed database, multiple distributed databases, a data store, a data lake, or an emergency backup database.
[0100] The memory 1025 may include random access memory (RAM) and read only memory (ROM). The memory 1025 may store computer-readable, computer-executable software that includes instructions that, when executed, cause the processor to perform various functions described herein. In some cases, the memory 1025 may include a basic input / output system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.
[0101] The processor 1030 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1030 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 1030. The processor 1030 may be configured to execute computer-readable instructions stored in the memory 1025 to perform various functions (e.g., functions or tasks supporting tenant-aware mTLS authentication).
[0102] FIG. 11 illustrates a flow chart illustrating a method 1100 for supporting tenant-aware mTLS authentication according to an aspect of the disclosure. The operations of method 1100 may be implemented by an application server or components thereof, as described herein. For example, the operations of method 1100 may be performed by a security manager, as described with reference to FIGS. 5-7. In some examples, the application server may execute a set of instructions to control functional elements of the application server to perform functions described herein. Additionally or alternatively, the application server may use dedicated hardware to perform aspects of the functionality described herein.
[0103] At 1105, an application server may receive an access request from a client to access a service by a service supported by a tenant of a multi-tenant system, the client being configured with a digital certificate chain associated with the tenant. The operations of 1105 may be performed according to methods described herein. In some examples, aspects of the operations of 1105 may be performed by an access request interface, as described with reference to FIGS. 5-7.
[0104] At 1110, the application server may send a first redirection response to the client indicating the mutual transport layer security service based on failure to receive a valid indication by the service that the client is authorized to access the service. The operations of 1110 may be performed according to methods described herein. In some examples, aspects of the operations of 1110 may be performed by an access component as described with reference to FIGS. 5-7.
[0105] At 1115, the application server may receive an indication of a digitally signed version of the digital certificate chain from the client, the digital certificate chain being signed using a root key associated with a mutual transport layer security service trusted by the most authentic. The operations of 1115 may be performed according to methods described herein. In some examples, aspects of the operations of 1115 may be performed by a certificate chain component, as described with reference to FIGS. 5-7.
[0106] At 1120, the application server may validate the digitally signed version of the digital certificate chain. The operation of 1120 may be performed according to methods described herein. In some examples, aspects of the operation of 1120 may be performed by a certificate validation component, as described with reference to FIGS. 5-7.
[0107] At 1125, the application server may send an indication to the client that the client is authorized to access the service based on validating the digitally signed version of the digital certificate chain. The operations of 1125 may be performed according to methods described herein. In some examples, aspects of the operations of 1125 may be performed by an authentication component, as described with reference to FIGS. 5-7.
[0108] FIG. 12 illustrates a flow chart illustrating a method 1200 for supporting tenant-aware mTLS authentication according to an aspect of the disclosure. The operations of method 1200 may be implemented by an application server or components thereof, as described herein. For example, the operations of method 1200 may be performed by a security manager, as described with reference to FIGS. 5-7. In some examples, the application server may execute a set of instructions to control functional elements of the application server to perform functions described herein. Additionally or alternatively, the application server may use dedicated hardware to perform aspects of the functionality described herein.
[0109] At 1205, an application server may receive an access request from a client to access a service by a service supported by a tenant of a multi-tenant system, the client being configured with a digital certificate chain associated with the tenant. The operations of 1205 may be performed according to methods described herein. In some examples, aspects of the operations of 1205 may be performed by an access request interface, as described with reference to FIGS. 5-7.
[0110] At 1210, the application server may determine that the access indicia presented by the client is invalid based on receiving the access request, and the service sends a first redirection response based on determining that the access indicia is invalid. The operations of 1210 may be performed according to methods described herein. In some examples, aspects of the operations of 1210 may be performed by an access validation component, as described with reference to FIGS. 5-7.
[0111] At 1215, the application server may send a first redirection response to the client indicating the mutual transport layer security service based on failure to receive a valid indication by the service that the client is authorized to access the service. The operations of 1215 may be performed according to methods described herein. In some examples, aspects of the operations of 1215 may be performed by an access component as described with reference to FIGS. 5-7.
[0112] At 1220, the application server may receive an indication of a digitally signed version of the digital certificate chain from the client, the digital certificate chain being signed using a root key associated with a mutual transport layer security service trusted by the most authentic. The operations of 1220 may be performed according to methods described herein. In some examples, aspects of the operations of 1220 may be performed by a certificate chain component as described with reference to FIGS. 5-7.
[0113] At 1225, the application server may validate the digitally signed version of the digital certificate chain. The operations of 1225 may be performed according to methods described herein. In some examples, aspects of the operations of 1225 may be performed by a certificate validation component, as described with reference to FIGS. 5-7.
[0114] At 1230, the application server may send an indication to the client that the client is authorized to access the service based on validating the digitally signed version of the digital certificate chain. The operations of 1230 may be performed according to methods described herein. In some examples, aspects of the operations of 1230 may be performed by an authentication component, as described with reference to FIGS. 5-7.
[0115] FIG. 13 illustrates a flow chart illustrating a method 1300 for supporting tenant-aware mTLS authentication according to an aspect of the disclosure. The operations of method 1300 may be implemented by a user device or components thereof, as described herein. For example, the operations of method 1300 may be performed by a security manager, as described with reference to FIGS. 8-10. In some examples, the user device may execute a set of instructions to control functional elements of the user device to perform functions described herein. Additionally or alternatively, the user device may use dedicated hardware to perform aspects of the functionality described herein.
[0116] At 1305, the user device may send an access request for accessing the service to a service supported by the tenant by a client, the client being configured with a client digital certificate chain associated with the tenant. The operations of 1305 may be performed according to methods described herein. In some examples, aspects of the operations of 1305 may be performed by an access component as described with reference to FIGS. 8-10.
[0117] At 1310, the user device may receive a first redirection response from the service indicating mutual transport layer security services based on a failure at the client to present a valid indication that the client is authorized to access the service. The operations of 1310 may be performed according to methods described herein. In some examples, aspects of the operations of 1310 may be performed by a redirection component as described with reference to FIGS. 8-10.
[0118] At 1315, the user device may perform a digital handshake with the mutual transport layer security service based on receiving the first redirection response, where performing the digital handshake includes sending an indication of a client digital certificate chain associated with the mutual transport layer security service. The operations of 1315 may be performed according to methods described herein. In some examples, aspects of the operations of 1315 may be performed by an mTLS component, as described with reference to FIGS. 8-10.
[0119] At 1320, the user device may receive a second redirection response from the mutual transport layer security service based on the digital handshake, the second redirection response including a digitally signed version of the client digital certificate chain, the digital certificate chain being signed using a private key associated with the mutual transport layer security service. The operations of 1320 may be performed according to methods described herein. In some examples, aspects of the operations of 1320 may be performed by a redirection component as described with reference to FIGS. 8-10.
[0120] At 1325, the user device may present, by the client, an indication of a digitally signed version of the client digital certificate chain based on receiving the second redirection response. The operations of 1325 may be performed according to methods described herein. In some examples, aspects of the operations of 1325 may be performed by a certificate chain component, as described with reference to FIGS. 8-10.
[0121] At 1330, the user device may receive an indication from the service that the client is authorized to access the service based on presenting an indication of a digitally signed version of the client digital certificate chain. The operations of 1330 may be performed according to methods described herein. In some examples, aspects of the operations of 1330 may be performed by an authentication component, as described with reference to FIGS. 8-10.
[0122] FIG. 14 illustrates a flow chart illustrating a method 1400 for supporting tenant-aware mTLS authentication according to an aspect of the disclosure. The operations of method 1400 may be implemented by a user device or components thereof, as described herein. For example, the operations of method 1400 may be performed by a security manager, as described with reference to FIGS. 8-10. In some examples, the user device may execute a set of instructions to control functional elements of the user device to perform functions described herein. Additionally or alternatively, the user device may use dedicated hardware to perform aspects of the functionality described herein.
[0123] At 1405, a user device may send an access request for accessing a service to a service supported by a tenant by a client, the client being configured with a client digital certificate chain associated with the tenant. The operations of 1405 may be performed according to methods described herein. In some examples, aspects of the operations of 1405 may be performed by an access component as described with reference to FIGS. 8-10.
[0124] At 1410, the user device may receive a first redirection response from the service indicating mutual transport layer security services based on a failure at the client to present a valid indication that the client is authorized to access the service. The operations of 1410 may be performed according to methods described herein. In some examples, aspects of the operations of 1410 may be performed by a redirection component as described with reference to FIGS. 8-10.
[0125] At 1415, the user device may receive from the user a selection of a client digital certificate chain issued or provisioned by the tenant, and a digital handshake is performed based on receiving the selection of the digital certificate chain. The operations of 1415 may be performed according to methods described herein. In some examples, aspects of the operations of 1415 may be performed by a user interface component, as described with reference to FIGS. 8-10.
[0126] At 1420, the user device may perform a digital handshake with the mutual transport layer security service based on receiving the first redirection response, where performing the digital handshake includes sending an indication of a client digital certificate chain associated with the mutual transport layer security service. The operations of 1420 may be performed according to methods described herein. In some examples, aspects of the operations of 1420 may be performed by an mTLS component, as described with reference to FIGS. 8-10.
[0127] At 1425, the user device may receive a second redirection response from the mutual transport layer security service based on the digital handshake, the second redirection response including a digitally signed version of the client digital certificate chain, the digital certificate chain being signed using a private key associated with the mutual transport layer security service. The operations of 1425 may be performed according to methods described herein. In some examples, aspects of the operations of 1425 may be performed by a redirection component as described with reference to FIGS. 8-10.
[0128] At 1430, the user device may present, by the client, an indication of a digitally signed version of the client digital certificate chain based on receiving the second redirection response. The operations of 1430 may be performed according to methods described herein. In some examples, aspects of the operations of 1430 may be performed by a certificate chain component, as described with reference to FIGS. 8-10.
[0129] At 1435, the user device may receive an indication from the service that the client is authorized to access the service based on presenting an indication of a digitally signed version of the client digital certificate chain. The operations of 1435 may be performed according to methods described herein. In some examples, aspects of the operations of 1435 may be performed by an authentication component, as described with reference to FIGS. 8-10.
[0130] A method of providing access to a service is described that may include receiving, by a service supported by a tenant of a multi-tenant system, an access request from a client to access the service, where the client is configured with a digital certificate chain associated with the tenant, sending, by the service, a first redirection response to the client indicating a mutual transport layer security service based on failure to receive a valid indication that the client is authenticated to access the service, receiving from the client an indication of a digitally signed version of the digital certificate chain, where the digital certificate chain is signed using a root key associated with a most authentically trusted mutual transport layer security service, validating the digitally signed version of the digital certificate chain, and sending to the client an indication that the client is authenticated to access the service based on validating the digitally signed version of the digital certificate chain.
[0131] An apparatus for providing access to a service is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive an access request from a client to access the service by a service supported by a tenant of a multi-tenant system, the client being configured with a digital certificate chain associated with the tenant; send a first redirection response to the client indicating a mutual transport layer security service based on failure to receive a valid indication by the service that the client is authenticated to access the service; receive from the client an indication of a digitally signed version of the digital certificate chain, the digital certificate chain being signed using a root key associated with a mutual transport layer security service trusted by a most authentic one; validate the digitally signed version of the digital certificate chain; and send an indication to the client that the client is authenticated to access the service based at least in part on validating the digitally signed version of the digital certificate chain.
[0132] Another apparatus for providing access to a service is described, which may include means for receiving an access request from a client to access the service by a service supported by a tenant of a multi-tenant system, the client being configured with a digital certificate chain associated with the tenant, means for sending a first redirection response to the client indicating a mutual transport layer security service based on failure to receive a valid indication by the service that the client is authenticated to access the service, means for receiving from the client an indication of a digitally signed version of the digital certificate chain, the digital certificate chain being signed using a root key associated with a most authentically trusted mutual transport layer security service, means for validating the digitally signed version of the digital certificate chain, and means for sending to the client an indication that the client is authenticated to access the service based at least in part on validating the digitally signed version of the digital certificate chain.
[0133] A non-transitory computer-readable medium storing code for providing access to a service is described, the code may include instructions executable by a processor to: receive, by a service supported by a tenant of a multi-tenant system, an access request from a client to access the service, the client configured with a digital certificate chain associated with the tenant, send, by the service, a first redirection response to the client indicating a mutual transport layer security service based on failure to receive a valid indication that the client is authenticated to access the service, receive from the client an indication of a digitally signed version of the digital certificate chain, the digital certificate chain signed using a root key associated with a most authentically trusted mutual transport layer security service, validate the digitally signed version of the digital certificate chain, and send to the client an indication that the client is authenticated to access the service based at least in part on validating the digitally signed version of the digital certificate chain.
[0134] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, validating a digitally signed version of a digital certificate chain may include acts, features, means, or instructions for validating a certificate chain associated with the digitally signed version of the digital certificate chain.
[0135] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, validating a digitally signed version of a digital certificate chain may include acts, features, means, or instructions for determining that an expiration date associated with the digital certificate chain may not have expired.
[0136] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for determining, based on receiving the access request, that an access indicia presented by the client may be invalid, and the service sending a first redirection response based on determining that the access indicia may be invalid.
[0137] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining that an access indicia may be invalid may include an operation, feature, means, or instruction for determining that a time-to-live value associated with the access indicia may not have expired.
[0138] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the access indicia includes a browser cookie, a JSON web token, an HTTP parameter, or a combination thereof.
[0139] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the instruction may include an operation, feature, means, or instruction for storing an access indicia at the client, the access indicia including a browser cookie, a JSON web token, an HTTP parameter, or a combination thereof.
[0140] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, services may be supported by tenants of a multi-tenant system that may be associated with mutual transport layer security services.
[0141] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a client digital certificate chain may be associated with a tenant based on the client digital certificate chain being issued or provisioned by a third-party certificate authority.
[0142] This section describes how to securely access the service. The method may include sending, by the client, to a service supported by the tenant, an access request for accessing the service, the client being configured with a client digital certificate chain associated with the tenant; receiving, at the client, from the service a first redirection response indicating a mutual transport layer security service based on a failure to present a valid indication that the client is authenticated to access the service; performing a digital handshake with the mutual transport layer security service based on receiving the first redirection response, the performing digital handshake including sending an indication of a client digital certificate chain associated with the mutual transport layer security service; receiving, based on the digital handshake, from the mutual transport layer security service, a second redirection response including a digitally signed version of the client digital certificate chain, the digital certificate chain being signed using a private key associated with the mutual transport layer security service; based on receiving the second redirection response, presenting, by the client, an indication of the digitally signed version of the client digital certificate chain; and receiving from the service an indication that the client is authenticated to access the service based on presenting the indication of the digitally signed version of the client digital certificate chain.
[0143] An apparatus for securely accessing a service is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may include causing the apparatus to: transmit, by a client, an access request for accessing the service to a service supported by a tenant, the client being configured with a client digital certificate chain associated with the tenant; receiving, at the client, a first redirection response from the service indicating a mutual transport layer security service based on a failure of the client to present a valid indication that the client is authorized to access the service; and performing a digital handshake with the mutual transport layer security service based on receiving the first redirection response, the performing the digital handshake including receiving an indication of the client digital certificate chain associated with the mutual transport layer security service. The method may be executable by the processor to cause the following to execute: sending; receiving a second redirection response from the mutual transport layer security service based on the digital handshake, the second redirection response including a digitally signed version of the client digital certificate chain, the digital certificate chain being signed using a private key associated with the mutual transport layer security service; presenting, by the client, an indication of the digitally signed version of the client digital certificate chain based on receiving the second redirection response; and receiving from the service an indication that the client is authenticated to access the service based on presenting the indication of the digitally signed version of the client digital certificate chain.
[0144] Another apparatus for securely accessing a service is described. The apparatus includes means for transmitting, by a client, an access request for accessing the service to a service supported by a tenant, the client being configured with a client digital certificate chain associated with the tenant; means for receiving, at the client, from the service a first redirection response indicating a mutual transport layer security service based on failure of the client to present a valid indication that the client is authorized to access the service; and means for performing a digital handshake with the mutual transport layer security service based on receiving the first redirection response, the performing the digital handshake including receiving a client digital certificate associated with the mutual transport layer security service. the client digital certificate chain, based on the digital handshake; means for receiving a second redirection response from the mutual transport layer security service including a digitally signed version of the client digital certificate chain, where the digital certificate chain is signed using a private key associated with the mutual transport layer security service; means for presenting, by the client, the indication of the digitally signed version of the client digital certificate chain based on receiving the second redirection response; and means for receiving from the service an indication that the client is authenticated to access the service based on the presentation of the indication of the digitally signed version of the client digital certificate chain.
[0145] A non-transitory computer readable medium storing code for securely accessing a service is described, the code comprising: transmitting, by a client, an access request for accessing the service to a service supported by a tenant, the client being configured with a client digital certificate chain associated with the tenant; receiving, at the client, a first redirection response from the service indicating a mutual transport layer security service based on a failure of the client to present a valid indication that the client is authorized to access the service; and performing a digital handshake with the mutual transport layer security service based on receiving the first redirection response, the performing the digital handshake including transmitting an indication of the client digital certificate chain associated with the mutual transport layer security service. and receiving, based on the digital handshake, a second redirection response from the mutual transport layer security service including a digitally signed version of the client digital certificate chain, the digital certificate chain being signed using a private key associated with the mutual transport layer security service; presenting, by the client, an indication of the digitally signed version of the client digital certificate chain based on receiving the second redirection response; and receiving from the service an indication that the client is authenticated to access the service based on the presentation of the indication of the digitally signed version of the client digital certificate chain.
[0146] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include acts, features, means, or instructions for presenting, by a client, an access indicia, where the client receives a first redirection response based on the access indicia being invalid.
[0147] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, an access indicia may be invalid based on a time-to-live value having expired.
[0148] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving an indication that the client may be authenticated may include an act, feature, means, or instruction for receiving an access indicia from the service, where the access indicia includes a browser cookie, a JSON web token, an HTTP parameter, or a combination thereof.
[0149] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include acts, features, means, or instructions for receiving from a user a selection of a client digital certificate chain issued or provisioned by the tenant, and a digital handshake may be performed based on receiving the selection of the digital certificate chain.
[0150] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a client digital certificate chain may be associated with a tenant based on the client digital certificate chain being issued or provisioned by a third-party certificate authority.
[0151] It should be noted that the methods described herein describe possible implementations, and that the acts and steps may be rearranged or otherwise modified, and other implementations are possible. Additionally, aspects from two or more of the methods may be combined.
[0152] The description set forth herein with respect to the accompanying drawings describes exemplary configurations and does not necessarily represent all examples that may be implemented or fall within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.
[0153] In the accompanying figures, similar components or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes between the similar components. If only a first reference label is used herein, the description is applicable to any of the similar components having the same first reference label, regardless of the second reference label.
[0154] The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0155] The various example blocks and modules described in connection with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
[0156] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored on or transmitted over a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of the software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. The features implementing the functions may also be physically located in various locations, including being distributed such that parts of the functions are implemented in different physical locations. Also, as used herein, including in the claims, "or" used in a list of items (e.g., a list of items preceded by an expression such as "at least one of" or "one or more of") indicates an inclusive list, such as, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" is intended to be interpreted the same as the phrase "based at least in part on."
[0157] Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that enables transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general purpose or special purpose computer. By way of example and not limitation, non-transitory computer-readable media can include RAM, ROM, Electrically Erasable Programmable Read-Only Memory (EEPROM), Compact Disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Also, any connection can be properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used herein, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where a disk typically reproduces data magnetically and a disc reproduces data optically with a laser. Combinations of the above are also included within the scope of computer readable media.
[0158] The description herein is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. 1. A method for providing secure access to a service, the method being performed by a server providing the service, the method comprising: receiving a request to access the service from a client of the service, the client being configured with a digital certificate chain that includes one or more digital certificates issued by one or more certificate authorities trusted by the service; sending a response to the client redirecting the client to a mutual transport layer security service trusted by the service based at least in part on determining that the client is not authorized to access the service; receiving from the client an indication of a digitally signed version of the digital certificate chain, wherein the indication of the digital certificate chain is sent by the client to the mutual transport layer security service based at least in part on the client receiving the response, and the digital certificate chain is digitally signed by the mutual transport layer security service using a private key of the mutual transport layer security service based at least in part on the mutual transport layer security service validating the digital certificate chain; validating that the digitally signed version of the digital certificate chain provided by the client is signed by the Mutual Transport Layer Security Service; sending to the client an indication of a valid access indicia indicating that the client is authorized to access the service based at least in part on validating the digitally signed version of the digital certificate chain provided by the client; The method includes:
2. Validating the digitally signed version of the digital certificate chain provided by the client includes: validating a chain of trust associated with the digitally signed version of the digital certificate chain that was signed by the mutual transport layer security service. The method of claim 1 , comprising:
3. Validating the digitally signed version of the digital certificate chain provided by the client includes: determining that a time to live associated with the digitally signed version of the digital certificate chain provided by the client has not expired. The method of claim 1 , comprising:
4. The step of determining that the client is not authorized to access the service comprises: determining that an access indicium presented by the client is invalid, and redirecting the client to the mutual transport layer security service is based at least in part on the client having an invalid access indicium. The method of claim 1.
5. The step of determining that the access indicia is invalid comprises: determining that a time-to-live value associated with the access indicia has expired, the time-to-live value being configured by a tenant supporting the service; The method of claim 4 , comprising:
6. The method of claim 1 , wherein the valid access indicia comprises a browser cookie, a JSON Web token, a HyperText Transfer Protocol (HTTP) parameter, or a combination thereof.
7. storing the valid access indicia at the client, the valid access indicia comprising a browser cookie, a JSON Web token, a HyperText Transfer Protocol (HTTP) parameter, or a combination thereof; The method of claim 1 further comprising:
8. The method of claim 1 , wherein the service is supported by a tenant of a multi-tenant system associated with the mutual transport layer security service.
9. The method of claim 1 , wherein the digital certificate chain issued by the certificate authority is associated with a tenant of a multi-tenant system that supports the service.
10. the service and the mutual transport layer security service are hosted by separate computing systems; the digitally signed version of the digital certificate chain signed by the mutual transport layer security service is associated with a first time-to-live value; the valid access indicia provided by the service are associated with a second time-to-live value that is greater than the first time-to-live value; The method of claim 1.
11. 1. A method for securely accessing a service, the method being performed by a client of the service, the method comprising: sending a request to access the service to a server providing the service, the client being configured with a digital certificate chain issued by a certificate authority trusted by the service; receiving a first response from the server redirecting the client to a mutual Transport Layer Security service trusted by the service; performing a digital handshake with the mutual transport layer security service based at least in part on receiving the first response, the performing the digital handshake including sending an indication of the digital certificate chain to the mutual transport layer security service; receiving a second response from the mutual transport layer security service, based at least in part on performing the digital handshake, the second response including a digitally signed version of the digital certificate chain, the digital certificate chain being digitally signed by the mutual transport layer security service using a private key of the mutual transport layer security service, based at least in part on the mutual transport layer security service validating the digital certificate chain, the second response redirecting the client to the service; sending an indication of the digitally signed version of the digital certificate chain to the server based at least in part on receiving the second response; receiving from the server an indication of a valid access indicia indicating that the client is authorized to access the service based at least in part on transmitting the indication of the digitally signed version of the digital certificate chain; The method includes:
12. transmitting an indication of an access indicia to the server, wherein the step of receiving the first response is based at least in part on the access indicia being invalid. The method of claim 11 further comprising:
13. The method of claim 12 , wherein the access indicia becomes invalid after a time-to-live value of the access indicia expires.
14. The method of claim 11 , wherein the valid access indicia includes a browser cookie, a JSON Web token, a HyperText Transfer Protocol (HTTP) parameter, or a combination thereof.
15. receiving a selection of the digital certificate chain issued by the certificate authority, wherein the digital handshake with the mutual transport layer security service is performed using the selected digital certificate chain; The method of claim 11 further comprising:
16. The method of claim 11 , wherein the digital certificate chain issued by the certificate authority is associated with a tenant of a multi-tenant system that supports the service.
17. 1. An apparatus for providing secure access to a service, comprising: A processor; a memory coupled to the processor; instructions stored in said memory; the instructions causing the device to: receiving a request for access to the service from a client of the service, the client being configured with a digital certificate chain issued by a certificate authority trusted by the service; sending a response to the client redirecting the client to a mutual transport layer security service trusted by the service based at least in part on determining that the client is not authorized to access the service; receiving from the client an indication of a digitally signed version of the digital certificate chain, where the indication of the digital certificate chain was sent by the client to the mutual transport layer security service based at least in part on the client receiving the response, and where the digital certificate chain is digitally signed by the mutual transport layer security service using a private key of the mutual transport layer security service based at least in part on the mutual transport layer security service validating the digital certificate chain; validating that the digitally signed version of the digital certificate chain provided by the client is signed by the Mutual Transport Layer Security Service; sending an indication of a valid access indicia to the client indicating that the client is authorized to access the service based at least in part on validating the digitally signed version of the digital certificate chain provided by the client; The apparatus is executable by the processor to cause
18. The instructions to validate the digitally signed version of the digital certificate chain provided by the client include instructions to the device to: Validating a chain of trust associated with the digitally signed version of the digital certificate chain provided by the client.
20. The apparatus of claim 17, executable by the processor to cause:
19. The instructions to validate the digitally signed version of the digital certificate chain provided by the client include instructions to the device to: determining that a time to live associated with the digitally signed version of the digital certificate chain provided by the client has not expired; 20. The apparatus of claim 17, executable by the processor to cause:
20. The instructions for determining that the client is not authorized to access the service include instructions for the device: determining that an access indicium presented by said client is invalid; 20. The apparatus of claim 17, executable by the processor to cause:
Citation Information
Patent Citations
Relativity authentication method and relativity authentication system
JP2004040650A
Network system
JP2007110377A
Apparatus, authentication system, server device, and authentication method
JP2017154492A
Cited By
Information processing device, information processing method, and program
JP2026177695A
