Native single sign-on (SSO) for mobile applications
AssigneeVerizon Patent and Licensing Inc.
InventorsGeorge Fletcher, Francis Hsu
Life of this patent
Estimating the term…
Abstract
Systems and methods for enhanced SSO, which can avoid faults in known protocols and standards for access delegation. For example, the enhanced SSO can use a shared security mechanism, such as a keychain or keystore, for sharing vendor identity over mobile applications without some of the pitfalls of using cookies. And, a connector code can bind the mobile applications to each other so that only the enhanced SSO is required for a user to log in to the mobile applications and remain logged in to the applications on one or more mobile devices.
Claims18
A method for enhanced single sign-on for mobile applications, the method comprising:
- transmitting, by a first mobile application, a request for an access token for the first mobile application to a remote server;
- receiving, by the first mobile application from the remote server, the access token for the first mobile application, a connector code and at least one other token from the remote server in response to the first mobile application's access token request;
- storing, by the first mobile application, in a shared security mechanism, the at least one other token and the connector code in a shared security mechanism;
- searching, by a second mobile application other than the first mobile application, in the shared security mechanism for the at least one other token and the connector code;
- and
- obtaining, by the second mobile application from the remote server, an access token for the second mobile application using a profile based at least in part on the at least one other token and the connector code received in connection with the first mobile application's authentication.
A non-transitory computer-readable storage medium tangibly encoded with computer-executable instructions, that when executed by a processor associated with a computing device, performs a method for enhanced single sign-on for mobile applications, the method comprising:
- receiving, by an authorization server and from a first mobile application, a request for an access token for the first mobile application;
- returning, by the authorization server, the access token for the first mobile application, a connector code and at least one other token to the first mobile application in response to the first mobile application's access token request, wherein the at least one other token and the connector code are stored in a shared security mechanism accessible by a second mobile application other than the first mobile application;
- receiving, by the authorization server and from the second mobile application, a request for an access token for the second mobile application, the request comprising a profile that is based at least in part on the at least one other token and the connector code;
- and
- using, by the authorization server, the profile that is based at least in part on the at least one other token and the connector code to generate an access token for the second mobile application.
A computing device comprising:
- a processor;
- and
- a non-transitory computer-readable storage medium for tangibly storing thereon program logic for execution by the processor, the program logic comprising:
- executable logic for receiving a request from a first mobile application for an access token for the first mobile application;
- executable logic for returning the access token for the first mobile application, a connector code and at least one other token to the first mobile application in response to the first mobile application's access token request, wherein the at least one other token and the connector code are stored in a shared security mechanism accessible by a second mobile application other than the first mobile application;
- executable logic for receiving, from the second mobile application, a request for an access token for the second mobile application, the request comprising a profile that is based at least in part on the at least one other token and the connector code;
- and
- executable logic for using the profile that is based at least in part on the at least one other token and the connector code to generate an access token for the second mobile application.
Dependencies are inferred from the claim text.