Hello,
We are in the process of testing enterprise single-sign-on for your iOS / Android mobile app and have a few questions:
1) Do you support federated authentication from your mobile app via SAML/OAuth/OpenID Connect? If Yes, which one method ?
2) Once the user is authenticated via federation, how often does the user get prompted for authentication again? (i.e., do you cache an authentication token so that the user is not prompted every time they launch the mobile app?)
3) Does your mobile app use any of the following embedded browsers for user-authentication. If Yes, which one?
4) Does your mobile app register an app URL scheme that can be invoked to complete enterprise SSO ? Typically an app registers a URL scheme that can be invoked with (SAML/OAuth) authentication token as a parameter. When such a URL is invoked, the mobile app completes the authentication flow with its backend web-service (via direct APIs or an embedded web-view) ?
Thanks
Hi Diego,
I personally can't answer all the Questions, but I can confirm that the mobile works together with our SAML Plugin, as we tested that recently.
Without having looked at it should work with most Plugins that work in a similar way, as the App uses the redirected login in a browser session.
For your reference our plugin you can find here: https://marketplace.atlassian.com/plugins/com.resolution.atlasplugins.samlsso.Confluence/server/overview
And more like it just by searching the marketplace on SAML.
The rest of your Questions, I leave Atlassian to answer.
Cheers,
Christian
Thanks for the response. There is another plug in that would work with Oauth as well and from experience from other services, these solutions sometimes only works on the site but not on the App.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Diego,
in my setup (resolution saml plugin, Android One) the auth token is not cached. I need to reauthenticate every time the Jira session expires which makes the mobile up unsuitable for our purposes.
I would like to fix this. Is there a way to get Chrome/Android to store and reuse the token?
Regards,
Kris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.