For those building mobile apps, the only enterprise question now is how does the authentication piece get added?
Well, we've got you covered there.
Today, we are unveiling the PingOne mobile app and a standard way to plug authentication into both web applications and applications designed to run natively on Android and iOS mobile platforms. There is no building, bailing wire, bad-mouthing or bellyaching. It just works.
End-users authenticate to an app on the phone, which then brokers SSO to the other applications the user wants to access.
The initial plan is to cover every application supported by the PingOne platform with the end goal being SSO to every SaaS or enterprise-built native app in existence. That's coming.
In the initial UI, we provide an app launcher interface that gives easy access to the business apps workers need on their mobile devices and tablets. Additionally, we have tabbed navigation, allowing users to sign-on and move between different applications without having to re-authenticate. That will be augmented in an update to be released shortly with the ability to re-organize and re-sort applications, mark apps as favorites and search for applications.
Under the covers, the client uses OAuth to maintain session. The client is built with an eye on future support for the under-construction OpenID Foundation NAPPS specification, which defines a standards-based native SSO token-issuing agent.
Today, mobile end-users and enterprises alike spend time trying to jump a gap in mobile authentication that either lacks for SSO or has a suspect end-user experience. With the PingOne native application, users can authenticate in a way that they are accustomed to for browser-based applications.
While PingOne and PingFederate users can leverage existing infrastructure to support native mobile SSO, the client takes it one step further by requesting and being granted a token that authorizes the device to initiate SSO to all applications the user is entitled to access.
This eliminates the need for the user to authorize and possibly re-authenticate for each native application individually that wish to launch. Additionally, since the PingOne native application is built on standards, it can leverage PingOne, PingFederate, or any independent SAML 2.0 compliant IdP platforms built by other vendors to perform the actual authentication of the user.
The result is a solution for the mobile workforce that allows them to conveniently use their SaaS apps just by remembering a single password connected to their mobile device.