- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2017 01:11 PM
Hey Everyone,
We are about to upgrade to Istanbul this weekend and there have been questions of using the mobile app.
We are going from Geneva patch 8 hotfix 1 to Istanbul.
I know the Mobile app has been available to Geneva Patch 6 and later.
However, we are not allowing use of the mobile app at this point due to the SAML authentication.
We currently have SAML setup in our organization. We are able to login to ServiceNow using the SAML server in the DMZ from any computer.
If you are not logged into the Domain computer as yourself, you are prompted to enter your network credentials.
However, when using the Mobile app, you have to have a password set within ServiceNow, which defeats the purpose of the SAML authorization.
In Android there is no option to set any type of authorization. it specificially asks for an instance, a username and password.
Is there not a way to use SAML authorization from the Android Mobile App?
We are not putting SSO software on anyone's phones/tablets, so that is not an option. We have a lot of mobile users who would like to use this option and not carry a computer around.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2017 01:33 PM
Hi Steven,
Are you using the MultiSSO plugin or the old SAML plugin?
I think the old SAML plugin is not compatible. From memory when we had the old plugin we were prompted for local account and password and after the installation of the new plugin (and a few configuration adjustments as setting a default identity provider), the mobile app started to try to connect to the SSO.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2017 01:33 PM
Hi Steven,
Are you using the MultiSSO plugin or the old SAML plugin?
I think the old SAML plugin is not compatible. From memory when we had the old plugin we were prompted for local account and password and after the installation of the new plugin (and a few configuration adjustments as setting a default identity provider), the mobile app started to try to connect to the SSO.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2017 01:02 PM
thank you for that. i have taken steps to switch to the multi provider SSO plugin from the old SAML plugin.
will update after we have made the switch.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2018 02:02 PM
How did it work out?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2018 02:30 PM
Well, were were in the process on converting to the multi provider sso plugin, from the old SAML authentication.
and we planned an implementation and the date got pushed back.
and we planned another date, and it got pushed back.
this happened for months for issues out of our control.
We finally just switched over at the same time we upgraded to Jakarta, just threw everything in at the same time and implemented it.
no one even noticed. it works like it should.
Switching over the new MPSSO did work and allows us to login to the mobile app via SAML authentication instead of local SN login.
