WEB-based identity authentication for desktop applications
By loading browser controls in desktop applications and using web applications as intermediaries, the problem of SAML technology being limited to web applications is solved, and the user authentication of desktop applications in online and offline modes is realized, which improves the flexibility and scalability of authentication.
Patent Information
- Application Number
- CN202280094160.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-30
- Publication Date
- 2024-11-12
Smart Images

Figure CN118947087A_ABST
Abstract
Description
Technical Field
[0001] Some embodiments described herein relate to computer applications, and more particularly, to using a web-based identity server to facilitate authentication of users to desktop applications. Background Art
[0002] Security Assertion Markup Language (SAML) is an open standard for exchanging authentication data between entities. For example, SAML is commonly used to authenticate users to web applications associated with service providers. A service provider is an entity that provides services, such as a utility. A service provider can be associated with a web application, such as a web application that can be used by a service provider's customers to check accounts or can be used by employees to perform maintenance tasks. If a web application requires user authentication, the web application can communicate with the identity server of the identity provider. An identity provider is an entity that provides authentication services. Using SAML, a web application exchanges communications with an identity server to authenticate users of a web application. The benefit of using SAML and therefore being able to exchange messages with an identity server is that a service provider does not need to implement its own authentication service, and in addition, a given identity server can be used to authenticate users to multiple web applications, which is convenient for users. Summary of the invention
[0003] In one embodiment, a desktop application performs various aspects of a method for authenticating a user. According to the method, when installed and run on a client device, the desktop application identifies a web application configured to act as an intermediary between the desktop application and an identity server. The desktop application loads a browser control to navigate the desktop application's internal browser to the web application, and the web application redirects the internal browser to the identity server. The desktop application submits user credentials to the identity server via the internal browser to authenticate the user of the desktop application. At its internal browser, the desktop application receives a small text file (cookie) including an access token for the user of the desktop application. The desktop application sends an authentication request including the access token to a web application programming interface (API) associated with the web application. The desktop application authorizes access to the resources of the desktop application based on the authentication indication received from the web API.
[0004] In another embodiment, a web application performs various aspects of a method for authenticating a user. According to the method, the web application receives a connection from an internal browser running in a desktop application of a client device. The web application redirects the internal browser of the desktop application to an identity server, and the web application acts as an intermediary between the desktop application and the identity server. The web application receives an indication at the desktop application that the user has successfully authenticated the identity server. In this way, the web application returns a cookie to the internal browser of the desktop application, which includes an access token confirming permission for the user at the desktop application. A web API associated with the web application receives an authentication request including an access token from the desktop application, and the web API authenticates the user to the desktop application based on the access token.
[0005] In another embodiment, a system configured to authenticate a user to a desktop application includes a web application and a desktop application. The web application is configured to act as an intermediary between the desktop application and an identity server for authenticating a user of the desktop application. The desktop application identifies the web application as an intermediary between the desktop application and the identity server. The desktop application loads a browser control to navigate an internal browser of the desktop application to the web application, and the web application redirects the internal browser to the identity server. The desktop application submits user credentials to the identity server via the internal browser to authenticate the user of the desktop application. The desktop application receives a cookie at the internal browser, which includes an access token for the user of the desktop application. The desktop application sends an authentication request including an access token to a web API associated with the web application. The desktop application authorizes access to resources of the desktop application based on the authentication indication received from the web API.
[0006] Mentioning these illustrative aspects and features is not intended to limit or define the presently described subject matter, but rather to provide examples to aid in understanding the concepts described in this application. Other aspects, advantages, and features of the presently described subject matter will become apparent after reviewing the entire application. BRIEF DESCRIPTION OF THE DRAWINGS
[0007] These and other features, aspects and advantages of the present disclosure will be better understood when the following detailed description is read with reference to the accompanying drawings.
[0008] Figure 1 is a diagram of an authentication system for authenticating a user to a desktop application according to some implementations described herein.
[0009] Figure 2 is a flow chart of a method of authenticating a user to a desktop application according to some implementations described herein.
[0010] Figure 3is a flow chart of a method of authenticating a user to a desktop application in offline mode according to some implementations described herein.
[0011] Figure 4 is a diagram of an example of a computing system that can perform certain operations described herein. DETAILED DESCRIPTION
[0012] Although Security Assessment Markup Language (SAML) provides convenience for both service providers and end users, a significant disadvantage of SAML is that it is generally limited to use with web applications. Many web applications support SAML by incorporating the configuration required to communicate in SAML into their code. In contrast, desktop applications are generally not designed to use SAML, so each existing desktop application that could potentially use an identity provider for authentication will need to be updated with the appropriate configuration in order to take advantage of SAML. Without this configuration, many desktop applications are severely limited in their authentication options.
[0013] However, some embodiments described herein facilitate the use of an identity provider to authenticate a user to a desktop application. For example, a desktop application can utilize a browser control to communicate with a web application so that the web application communicates with an identity server using SAML on behalf of the desktop application. In addition, in some embodiments, a web application programming interface (API) associated with the web application can generate a temporary password to enable authentication of the user in an offline mode. As a result, the desktop application can authenticate the user in both online and offline modes in conjunction with the identity server through SAML. Another benefit of some embodiments is scalability, as the desktop application can be configured to use different authentication technologies or different identity providers simply by being directed to a different web application configured to facilitate the desired authentication.
[0014] Figure 1 1 is a diagram of an authentication system 100 according to some embodiments described herein. The authentication system 100 may include a desktop application 110, an identity server 120, a web API 130, and a web application 140 associated with the web API 130, each of which may be connected to a network 150. The desktop application 110, the identity server 120, the web API 130, and the web application 140 may communicate with each other as needed or as described herein to enable the desktop application 110 to authenticate a user. The authentication system 100 may enable the desktop application 110 to authenticate a user of the desktop application 110 by communicating with the identity server 120 using SAML. In some embodiments, the desktop application is not configured to support SAML. However, the web application 140 may act as an intermediary between the desktop application 110 and the identity server 120 to facilitate authentication.
[0015] Desktop application 110 may be installed on client device 160, which may be a computing device such as a desktop computer, a laptop computer, a tablet computer, or a smart phone. Desktop application 110 may be a software program or a portion of a software program that is executable by a processor of client device 160, such that desktop application 110 runs on client device 160. For example, desktop application 110 is a thick client application.
[0016] In some embodiments, the desktop application 110 is associated with a service provider. For example, the service provider is a utility provider, and the desktop application 110 is a program used by field technicians of the utility provider to manage and track the maintenance of utility meters. However, various other types of desktop applications 110 are also within the scope of the present disclosure. The desktop application 110 may require user authentication, so that the resources 170 of the desktop application (such as data or services provided by the desktop application 110) are not accessible to the user until the user authenticates himself to the desktop application 110.
[0017] In some embodiments, the desktop application 110 is configured to execute a browser control 180 to provide an internal browser 190 in the desktop application 110. For example, the browser control 180 can provide controls, such as navigation controls, that enable the web browsing functionality of the internal browser 190 in the desktop application 110. In other words, the browser control 180 can be a browser wrapper for the desktop application 110. Because the internal browser 190 is part of the desktop application 110, in some embodiments, the internal browser 190 does not have the configuration required to support SAML. Therefore, in some embodiments, the internal browser 190 cannot communicate directly with the identity server 120 to authenticate the user. However, as described herein, the internal browser 190 can communicate with the web application 140 to facilitate user authentication.
[0018] The identity server 120 may be configured to authenticate the user by verifying the user's identity. More specifically, the identity server 120 may authenticate the user's identity based on the user's credentials entered by the user to match the identity of the user associated with the user account on the identity server 120. The identity server 120 may be a server associated with an identity provider. Through the identity server 120, the identity provider may confirm the user's identity, and thus may authenticate the user to various applications. These applications may be web applications, desktop applications, or a combination of the two. The identity server 120 may be implemented as hardware, software, or a combination of the two. The identity server 120 may be implemented on a computing device or distributed across two or more computing devices. For example, the identity server 120 may be implemented as a program code executed on one or more processors of one or more computing devices. In some embodiments, the identity server 120 operates in the cloud and may be accessed via the Internet.
[0019] The identity server 120 may include or have access to a data store 125 that maintains information about users who have user accounts on the identity server 120. The data store 125 may be one or more databases, database tables, text files, or other storage objects stored in a storage device of the identity server 120. For example, each user account may be represented as a table row in the data store 125. In some implementations, a user account includes user data related to a corresponding user, wherein the user data includes authentication data for authenticating a user associated with the user account.
[0020] For example, the authentication data in the user account of the user may include a user identifier and a password. The user identifier may uniquely identify the user; for example, the user identifier is an email address, a password, a phone number, an Internet Protocol (IP) address, a media access control (MAC) address, or other data. The password may be stored in the data store 125 in an encrypted, hashed, or otherwise hidden form. In some embodiments, such as if the identity server 120 supports biometric data, the authentication data in the user account may additionally or alternatively include a representation of the user's biometric factor, which may be hashed or otherwise hidden. When initially establishing or updating a user account, the identity server 120 may receive the authentication data, such as by manual input by a user or administrator. The identity server 120 may then maintain the authentication data in the data store 125 for use in authenticating the user as described herein.
[0021] The identity server 120 may be configured to communicate with applications using SAML. In some embodiments, the identity server 120 may not be able to communicate directly with certain desktop applications or web applications that do not support SAML for authentication purposes. Furthermore, in some embodiments, the desktop application 110 described herein does not need to support SAML. The web application 140 may manage user authentication of the desktop application 110 by communicating with the desktop application 110 and further communicating with the identity server 120 using SAML. Although the present disclosure specifically and repeatedly mentions the use of SAML, various embodiments may use some other secure communication protocols. Therefore, the embodiments described herein are not limited to SAML as the secure communication protocol for the identity server 120, but references to SAML herein are specifically for illustrative purposes only.
[0022] The web application 140 can be configured to act as an intermediary between the desktop application 110 and the identity server 120 to authenticate the user of the desktop application 110. In some embodiments, the web application 140 is implemented as hardware, software, or a combination of both. For example, the web application 140 is implemented as a program code stored on a storage device and executable by one or more processors. The web application 140 can be run locally, such as at a site associated with a service provider associated with the desktop application 110, or can be operated in the cloud. In some embodiments, the web application 140 is configured to communicate with the identity server 120 using SAML. For example, the program code of the web application 140 includes instructions for parsing and constructing SAML statements. In this way, the web application 140 is configured to exchange messages with the identity server 120 for authentication purposes.
[0023] In some embodiments, the web API 130 is an application programming interface exposed to the desktop application 110. The web API 130 can act as an interface for the desktop application 110 to perform certain interactions with the web application 140 or with other resources on the web. In some embodiments, the web API 130 is implemented as hardware, software, or a combination of both. The web API 130 can be run locally, such as at a site associated with a service provider associated with the desktop application 110, or can be operated in the cloud. In some embodiments, the web API 130 is integrated with the web application 140, or the web API 130 is executed on the same one or more computing devices as the web application 140. However, additionally or alternatively, the web API 130 can be run on a different device from the web application 140, and can communicate with the web application 140 through the network 150 or via other means.
[0024] In some implementations, each of the web application 140, web API 130, and identity server 120 can facilitate authentication for multiple desktop applications. In this case, each desktop application configured to use the authentication system 100 as described herein can access the web API 130 and web application 140, and can perform operations similar to those performed by the desktop application 110 described herein. Thus, although the present disclosure repeatedly refers to operations involving desktop application 110 in the singular, the authentication system 100 can authenticate users against various desktop applications 110, and such authentication can occur in parallel, such that the web application 140, web API 130, and identity server 120 can facilitate authentication for multiple desktop applications 110 at a given time.
[0025] In some implementations, desktop application 110, web application 140, web API 130, and identity server 120 communicate with each other via network 150. Network 150 may be a combination of one or more local area networks or wide area networks using a wired communication system, a wireless communication system, or a combination thereof. Each of client device 160, web application 140, web API 130, and identity server 120 may access network 150 directly or indirectly via a corresponding network interface device.
[0026] Figure 2 1 is a flow chart of a method 200 for authenticating a user to a desktop application 110 according to some embodiments described herein. In some embodiments, when the desktop application 110 is launched on the client device 160, components of the authentication system 100 perform the method 200 or a similar method. Figure 2 , the flowchart is divided into four vertical regions across the horizontal axis, each vertical region representing an operation performed by a corresponding component of the authentication system 100. However, the assignment of operations to certain components is provided only for illustrative purposes and does not limit the various possible implementations of the authentication system 100.
[0027] Figure 2 The method 200 depicted in FIG. 2 may be implemented in software executed by one or more processors of a computer system, in hardware, or in a combination of software and hardware. Figure 2 The method 200 presented in and described below is intended to be illustrative and not limiting. Figure 2 Various processing operations are depicted as occurring in a particular order or sequence, but this is not intended to be limiting. In some alternative examples, processing may be performed in a different order, operations may be excluded or added, or some operations may be performed in parallel.
[0028] Prior to block 205, the desktop application 110 may determine whether it can reach the web API 130, which is required for online authentication in some implementations. For example, if the client device 160 on which the desktop application 110 is running is not connected to the network 150, or otherwise, if the desktop application 110 does not have network access rights, the desktop application 110 may not be able to reach the web API 130. If the desktop application 110 cannot reach the web API 130, the desktop application may perform a method 300 for authenticating in an offline mode, such as Figure 3 However, if the desktop application 110 can reach the webAPI 130, the desktop application 110 can continue the method 200 in an online mode.
[0029] like Figure 2 As shown, at block 205, the desktop application 110 identifies a web application 140 configured to act as an intermediary between the desktop application 110 and the identity server 120. To this end, the desktop application 110 may request authentication settings required for authentication; for example, the desktop application 110 may request such authentication settings from the web API 130. In response to the request, the web API 130 may return the authentication settings.
[0030] The authentication settings may identify the web application 140 to the desktop application 110. In some examples, the authentication settings explicitly provide the location of the web application 140 to be used for authentication, such as a uniform resource locator (URL) or an IP address. Additionally or alternatively, in some examples, the desktop application 110 maintains a mapping of secure communication protocols to web applications, and the desktop application 110 knows the location of such web applications. In this case, the authentication settings may indicate a secure communication protocol, such as SAML, and the desktop application 110 may map the secure communication protocol to the location of the web application 140. Various implementations are possible and within the scope of the present disclosure.
[0031] At block 210, the desktop application 110 loads the browser control 180 to navigate the internal browser 190 of the desktop application 110 to the web application 140 identified at block 205. At block 215, the web application 140 may redirect the internal browser 190 of the desktop application 110 to the identity server 120. In some implementations, the web application 140 includes program code that indicates the location (such as a URL or IP address) of the identity server 120, and therefore, the web application 140 may redirect the internal browser 190 to that location.
[0032] At block 220, the identity server 120 receives a connection from the internal browser 190 of the desktop application 110. Specifically, the connection may be a result of the internal browser 190 having been redirected to the identity server 120 by the web application 140. Thus, at block 225, the identity server 120 sends a prompt to provide user credentials to the internal browser 190 of the desktop application 110. In some implementations, the prompt is displayed to the user via the internal browser of the desktop application 110, and the user enters the user's credentials into the internal browser 190.
[0033] At block 230, the desktop application 110 sends the user credentials to the identity server 120 via the internal browser 190. At block 235, the identity server 120 receives the user credentials and confirms the identity of the user. More specifically, the identity server 120 may confirm that the received user credentials match the user credentials in the authentication data of the user account stored in the data store 125 of the identity server 120. However, if the user credentials do not match the authentication data stored in the data store 125, the identity server 120 may send a prompt for the user credentials again or may indicate that the authentication has failed.
[0034] If the user credentials are valid (i.e., match the authentication data of the user account), then at box 240, the identity server 120 redirects the internal browser 190 back to the web application 140. Then, at box 245, the web application 140 generates a cookie (e.g., a data block) including an access token and sends the cookie to the internal browser 190 of the desktop application. In some embodiments, the access token is encrypted to ensure that the access token cannot be stolen and used by a different user to access the desktop application 110. The access token can be or include identification data that confirms the authentication and uniquely identifies the session between the user and the desktop application 110. For example, the access token may include a random string unique to the session. Conventionally, after authenticating the user to the web application, the web browser couples communications from the client side with metadata including the access token to confirm the authenticity of such communications. However, in some embodiments, the access token is utilized by the desktop application 110 without additional action by the internal browser 190 (e.g., after the internal browser 190 is closed), as described further below.
[0035] At block 250, the desktop application 110 stores the cookie locally. In some implementations, the desktop application 110 can then close the internal browser 190. At block 255, the desktop application 110 sends an authentication request to the web API 130. In some implementations, the desktop application 110 sends an access token, which can be encrypted, as part of the authentication request to the web API 130.
[0036] At box 260, the web API 130 receives an authentication request including an access token. The web API 130 may be configured to authenticate the access token, for example by verifying the authenticity of the access token. In addition, the web API 130 may maintain or access a mapping of the user to the permissions of the desktop application 110. Given the access token, which may include a user identifier that identifies the user, the web API 130 may therefore authenticate the access token and determine the permissions associated with the user. At box 265, the web API 130 sends an authentication notification to the desktop application 110, indicating that the user is authenticated with specific permissions. The authentication notification may indicate specific permissions that apply to the user relative to the desktop application 110, such as which resources 170 the user is allowed to read and which resources 170 the user is allowed to write.
[0037] At box 270, web API 130 generates a temporary password for the user of desktop application 110 and sends a representation of the temporary password (such as a hash of the temporary password) to the desktop application. At box 275, web API 130 also sends the temporary password to the user, such as via email, so the user has the temporary password. As described in more detail below, the temporary password can enable the user to log into desktop application 110 in offline mode.
[0038] At block 280, desktop application 110 receives the authentication notification and a representation of the temporary password. Desktop application 110 may store the representation of the temporary password locally. In some implementations, client device 160 includes a secure storage device, such as an encrypted drive, and desktop application 110 causes client device 160 to store the representation of the temporary password on the secure storage device.
[0039] At block 285, the desktop application 110 allows the user to access the resource 170 according to the specific permissions indicated in the authentication notification received at block 280. For example, the desktop application 110 displays a user interface through which the user can access the resource 170 or perform other activities available through the desktop application 110 if the specific permissions are provided. In some implementations, this begins a session between the user and the desktop application 110.
[0040] Typically, in some implementations, a session is a limited period of time during which a user interacts with the desktop application 110 without having to reauthenticate. Later, the desktop application 110 may automatically terminate the session, for example, in response to a user logging out or after a user's inactivity period reaches a certain length of time. After the session is terminated, the user may need to reauthenticate to access the resources 170 of the desktop application 110 again, and this reauthentication may be accomplished as described above or using a temporary password.
[0041] In some implementations, the above-described communications occurring between desktop application 110, web API 130, and web application 140 may be transparent to the user. For example, the user opens desktop application 110, sees a prompt for user credentials, enters the user credentials, receives an email indicating a temporary password for offline login, and is allowed access to resource 170. The user does not need to be aware of the various other operations involved in authentication method 200.
[0042] As described above, the desktop application 110 may provide or restrict access to resources 170 (such as certain data or services). In some cases, a user may need to access the resource 170 where the desktop application 110 cannot reach the web API 130 through the network 150. For example, the desktop application 110 may not always have network access rights. In one example, the client device 160 is a mobile device, and the user, who is a field technician, needs to use the desktop application 110 when on site. In this example, the resource 170 accessible to the desktop application 110 may be information about activities that need to be performed by the field technician. However, when operating on site, network access rights may not always be available for the desktop application 110.
[0043] Some embodiments of the desktop application 110 utilize temporary passwords discussed above with reference to blocks 270-280 to facilitate user authentication in offline mode. Each temporary password can be associated with an expiration time. Before the expiration time is reached, the temporary password remains valid for identity authentication in offline mode. However, when the expiration time of the password is reached, the temporary password expires, thus becoming invalid, and can no longer be used for authentication.
[0044] Figure 3 1 is a flow chart of a method 300 for authenticating a user to a desktop application 110 in offline mode according to some embodiments described herein. In some embodiments, the desktop application 110 performs the method 300 or a similar method when the desktop application 110 is launched on the client device 160 and detects that the web API 130 is not reachable. In this case, the desktop application 110 can proceed to the method 300 to authenticate in offline mode.
[0045] Figure 3 The method 300 depicted in can be implemented in software executed by one or more processors of a computer system, in hardware, or in a combination of software and hardware. Figure 3 The method 300 presented in and described below is intended to be illustrative and not limiting. Figure 3Various processing operations are depicted as occurring in a particular order or sequence, but this is not intended to be limiting. In some alternative examples, processing may be performed in a different order, operations may be excluded or added, or some operations may be performed in parallel.
[0046] like Figure 3 As shown, at box 305, the desktop application 110 prompts the user to enter user credentials. For example, the desktop application 110 presents a user interface to the user, which includes an input element where the user can type and submit or otherwise enter user credentials. In some examples, the user credentials include a user identifier and a password. At box 310, the desktop application 110 receives the user credentials entered by the user in response to the prompt.
[0047] At decision block 315, the desktop application 110 determines whether any temporary password associated with the user (e.g., associated with the input user identifier) is stored on the client device 160 and is valid for offline authentication. For example, a temporary password may be considered valid if it has not expired, and a temporary password may be considered invalid after it expires. If no such valid temporary password is found, then at block 320, authentication fails. The desktop application 110 may present a notification, such as via a user interface, that authentication in offline mode is unavailable or has failed. In this case, the desktop application 110 may limit or disallow access to resources 170 available through the desktop application 110.
[0048] However, if at least one temporary password is found to be valid for the user on the client device 160, then at decision block 325, the desktop application 110 compares the temporary password to the password entered by the user as part of the user credentials. As described above, the client device 160 may maintain a hash of the temporary password, rather than the temporary password itself. In this case, the desktop application 110 may hash the password received at block 310 and may compare the hash to the hash of the temporary password to determine whether the received password matches the temporary password.
[0049] If the received password does not match the temporary password, then at block 330, authentication fails because the received user credentials are invalid. In this case, the desktop application 110 may indicate, such as via a user interface, that authentication has failed. The desktop application 110 may limit or disallow access to resources 170 available through the desktop application 110 until the user enters valid user credentials. In some implementations, the desktop application 110 may allow the user one or more additional attempts to provide valid user credentials.
[0050] However, if the password received at block 310 matches the temporary password associated with the user, then at block 335, the desktop application 110 deems the user to be authentic. In this way, the desktop application can allow the user to use the desktop application 110 to access resources 170 or perform other activities.
[0051] Figure 4 is a diagram of an example of a computing system 400 that can perform certain operations described herein. For example, similar to Figure 4 The illustrated computing system 400 may be a client device 160 configured to run desktop application 110, computing system 400 may run web application 140 and web API 130, or computing system 400 may be or may execute identity server 120. Various suitable computing systems or groups of computing systems may be used to perform the operations described herein.
[0052] For example, Figure 4 An example of a computing system 400 acting as a client device 160 and executing a desktop application 110 is shown. The depicted example of computing system 400 includes a processor 402 communicatively coupled to one or more memory devices 404. Processor 402 executes computer executable program code stored in memory device 404. Examples of processor 402 include a microprocessor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or another suitable processing device. Processor 402 may include one or more processing devices.
[0053] Memory device 404 includes suitable non-transitory computer-readable media for storing data, program code, or both. Computer-readable media may include electronic, optical, magnetic, or other storage devices capable of providing computer-readable instructions or other program code to the processor. Non-limiting examples of computer-readable media include disks, memory chips, read-only memories (ROMs), random access memories (RAMs), optical storage devices, magnetic tapes or other magnetic storage devices, or another medium from which a processing device can read instructions.
[0054] In some embodiments, the computing system 400 executes program code that configures the processor 402 to perform one or more operations described herein. The program code includes, for example, instructions for implementing the desktop application 110 or other suitable system for performing one or more operations described herein. The program code may reside in the memory device 404 or a suitable computer-readable medium and may be executed by the processor 402 or other suitable processor. Although not described herein, the program code may be executed by the processor 402 or other suitable processor. Figure 4 4, but a memory device 404 of the same or a different computing system 400 may include program code for the web application 140 or the web API 130 or both.
[0055] The computing system 400 may include one or more external or internal devices, such as input or output devices. For example, the computing system 400 is shown as having one or more input / output ("I / O") interfaces 408. One or more buses 406 are also included in the computing system 400. The bus 406 communicatively couples one or more components of the computing system 400.
[0056] Implementation of computing system 400 includes network interface device 410. Network interface device 410 includes one or more devices suitable for establishing a wired or wireless data connection to one or more data networks, such as network 150. Non-limiting examples of network interface device 410 include an Ethernet network adapter or a wireless fidelity (WiFi) card. Computing system 400 can communicate with one or more other computing devices via a data network using network interface device 410. For example, computing system 400 running desktop application 110 can communicate with web application 140 and web API 130 via network 150 using network interface device 410.
[0057] Numerous specific details are set forth herein to provide a thorough understanding of the claimed subject matter. However, those skilled in the art will appreciate that the claimed subject matter may be practiced without these specific details. In other cases, methods, devices, or systems known to those skilled in the art are not described in detail to avoid obscuring the claimed subject matter.
[0058] The features discussed herein are not limited to any particular hardware architecture or configuration. A computing device may include any suitable arrangement of components that provide a result conditioned on one or more inputs. Suitable computing devices include a multi-purpose microprocessor-based computer system that accesses stored software (i.e., computer-readable instructions stored on a computer system's memory), which programs or configures the computing system from a general-purpose computing device to a dedicated computing device that implements one or more aspects of the present subject matter. Any suitable programming, scripting, or other type of language or language combination may be used to implement the teachings contained herein in software for programming or configuring a computing device.
[0059] Aspects of the methods disclosed herein may be performed in the operation of such a computing device. The order of the blocks presented in the above examples may be changed; for example, the blocks may be reordered, combined, and / or divided into sub-blocks. Certain blocks or processes may be performed in parallel.
[0060] The use of "suitable for" or "configured to" herein is meant to be open and inclusive language that does not exclude devices that are suitable for or configured to perform additional tasks or steps. In addition, the use of "based on" is meant to be open and inclusive, because a process, step, calculation or other action "based on" one or more of the stated conditions or values may, in practice, be based on additional conditions or values beyond the stated conditions or values. The headings, lists and numbers included herein are for ease of explanation only and are not meant to be limiting.
[0061] Although the subject matter has been described in detail with respect to specific aspects of the subject matter, it should be understood that those skilled in the art, after understanding the foregoing, can easily produce changes, variations and equivalents to these aspects. Therefore, it should be understood that the present disclosure is presented for the purpose of illustration rather than limitation, and does not exclude such modifications, variations and / or additions to the subject matter, which are obvious to those of ordinary skill in the art.
Claims
1. A method comprising: identifying a web application by a desktop application installed and running on a client device, the web application being configured to act as an intermediary between the desktop application and an identity server; loading, by the desktop application, a browser control to navigate an internal browser of the desktop application to the web application, wherein the web application redirects the internal browser to the identity server; Submitting user credentials by the desktop application to the identity server via the internal browser to authenticate a user of the desktop application; receiving, at the internal browser of the desktop application, a cookie comprising an access token for the user of the desktop application; The desktop application sends an authentication request including the access token to a web application programming interface API associated with the web application; as well as Access to resources of the desktop application is authorized based on the authenticated indication received from the web API.
2. The method according to claim 1, further comprising: Receiving, by the desktop application, a hash of a temporary password generated by the web API; as well as The hash of the temporary password is stored on the client device to enable offline authentication of the user to the desktop application.
3. The method according to claim 2, further comprising: terminating a session between the user and the desktop application; Receiving a password input at the desktop application; as well as Access to the resources of the desktop application is authorized based on the entered password matching the hash of the temporary password generated by the web API.
4. The method according to claim 1, wherein: Identifying the web application includes: requesting the web API to provide settings associated with the identity server to authenticate a user of a desktop application installed and running on the client device; and An indication is received by the desktop application from the web API that the web application is to act as an intermediary between the desktop application and the identity server.
5. The method according to claim 4, further comprising: receiving, by the desktop application, an indication of a secure communications protocol for communicating with the identity server; as well as The web application is identified as having the capability to use the secure communication protocol.
6. The method according to claim 4, further comprising: receiving, by the desktop application, an indication that Security Assertion Markup Language (SAML) is used for communications with the identity server; as well as The web application is identified as having the ability to communicate with the identity server using SAML.
7. A method comprising: receiving, at the web application, a connection from an internal browser running in a desktop application on a client device; redirecting, by the web application, the internal browser of the desktop application to an identity server, wherein the web application acts as an intermediary between the desktop application and the identity server; Receiving, by the web application at the desktop application, an indication that the user has successfully authenticated with the identity server; Returning a cookie by the web application to the internal browser of the desktop application, the cookie including an access token confirming permission of the user at the desktop application; receiving, from the desktop application, an authentication request including the access token; as well as The user is authenticated to the desktop application based on the access token.
8. The method according to claim 7, further comprising: generating a temporary password for an offline mode of the desktop application; as well as A hash of the temporary password is sent to the desktop application to enable offline authentication of the user to the desktop application.
9. The method according to claim 7, further comprising: receiving an authentication setup request from the desktop application via a web application programming interface (API) associated with the web application; as well as In response to the authentication setup request, an indication of the web application is sent to the desktop application.
10. The method of claim 7, further comprising communicating, by the web application on behalf of the desktop application, with the identity server using security assertion markup language.
11. A system comprising: a web application configured to act as an intermediary between a desktop application and an identity server for authenticating a user of the desktop application; Desktop applications are configured as: identifying the web application as an intermediary between the desktop application and the identity server; loading a browser control to navigate the internal browser of the desktop application to the web application, wherein the web application redirects the internal browser to the identity server; submitting user credentials to the identity server via the internal browser to authenticate a user of the desktop application; receiving, at the internal browser, a cookie comprising an access token for the user of the desktop application; Sending an authentication request including the access token to a web application programming interface (API) associated with the web application; as well as Access to resources of the desktop application is authorized based on the authenticated indication received from the web API.
12. The system of claim 11, wherein the web application is further configured to facilitate authentication of the user to a second desktop application, wherein the second desktop application is different from the desktop application.
13. The system according to claim 11, wherein: The web API is also configured to: generating a temporary password to enable offline authentication of the user to the desktop application; and A hash of the temporary password is sent to the desktop application.
14. The system according to claim 13, wherein: The desktop application is also configured to: receiving the hash of the temporary password generated by the web API; and The hash of the temporary password is stored on a client device running the desktop application to enable offline authentication of the user to the desktop application.
15. The system of claim 14, wherein: The desktop application is also configured to: terminating a session between the user and the desktop application; receiving a password input; and Access to the resource is authorized based on the entered password matching the hash of the temporary password generated by the web API.
16. The system of claim 11, wherein: In order to identify the web application as an intermediary between the desktop application and the identity server, the desktop application is further configured to: requesting the web API to provide settings related to the identity server; and An indication of the web application is received from the web API.
17. The system of claim 11, wherein: The desktop application is also configured to: receiving an indication of a secure communications protocol for communicating with the identity server; and The web application is identified as having the capability to use the secure communication protocol.
18. The system of claim 11, wherein: The desktop application is also configured to: receiving an indication that Security Assertion Markup Language (SAML) is used for communications with the identity server; and The web application is identified as having the ability to communicate with the identity server using SAML.
19. The system of claim 18, wherein: The web application is also configured to communicate with the identity server using SAML on behalf of the desktop application.
20. The system of claim 19, wherein: The desktop application lacks the ability to communicate using SAML.
