NATIVE SINGLE SIGN-ON (SSO) FOR MOBILE APPLICATIONS
FIG3 is a schematic block diagram illustrating components of an exemplary system in accordance with some embodiments of the present disclosure
FIG3 is a block diagram illustrating the components for performing the systems and methods discussed herein. FIG3 includes an authorization server 300 (such as authorization server 106), network 315 (such as network 105), a shared security mechanism 320 as well as first and second mobile applications 330 and 335 (e.g., mobile applications 244 and 245). The authorization server 300 can be a special purpose machine or processor and could be hosted by a messaging server, application server, content server, social networking server, web server, search server, content provider, email service provider, ad server, user's computing device, and the like, or any combination thereof. According to some embodiments, a database can be associated with the authorization server 300 (which is not shown in FIG3) and such a database can include information associated with content providers, such as, but not limited to, messaging platforms, applications, sites, or providers that enable users to send, receive, search for, upload, download, share, edit or otherwise avail users to content (e.g., Yahoo!® Search, Yahoo!® Mobile applications, Yahoo!® Mail, Flickr®, Tumblr®, Twitter®, Instagram®, SnapChat®, Facebook®, and the like). In some embodiments, such a database can comprise data and metadata associated with such information from one and/or an assortment of media hosting sites. In some embodiments, such content provider information can include, but is not limited to, versions, types and/or capabilities of applications that are resident or accessed by a user device, and/or are capable of being downloaded, executed, accessed or run on user device for purposes of rendering content.
schematic block diagram
335
applications application
300
server
315
network
320
shared security mechanism
330
applications application
['1. A method for enhanced single sign-on for mobile applications, the method comprising: requesting, by a first mobile application, an authorization server to return a connector code; receiving, by the first mobile application, the connector code with at least one token from a remote server; storing in a shared security mechanism, by the first mobile application, the at least one token; searching, by a second mobile application, in the shared security mechanism for the at least one token; and using, by the second mobile application, a profile to obtain a token for the second mobile application based on the at least one token and the connector code.']