
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-23-2016 10:49 AM
I am trying to configure my personal dev instance to use ssocircle. It is on Helsinki release. I have imported the metadata into the instance from http://idp.ssocircle.com/meta-idp.xml. I have also imported ServiceNow generated metadata into ssocircle account that I have. I manually created the ID that I am using in ssocircle in my instance with the same email address. I have also white-listed the links of ssocircle through 'glide.security.url.whitelist' property.
Now when I try 'Use external login' and enter my userid, it gives "Redirect failed, please contact your administrator." Tried dev tools of chrome to trace the request but nothing comes up.
Please let me know what am I missing?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-27-2016 08:43 AM
I was able to resolve it. Turns out that decoding needed another certificate. Adding it resolved the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-16-2017 12:55 AM
Great thanks.
In my case, both certificates imported by default, the only thing that was missing to make it work is to define newly added ssoCircle IdP as
default (=true) in the list of identity providers. After doing that, i was able to successfully login using my ssocircle account.
Could you explain in a few words regarding <NameIDFormat>. I know sso circle is using
urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
in their example, what would be the outcome of using the default:
urn:oasis:names:tc:SAML:2.0:nameid-format:entity
Thank you.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-16-2017 10:51 AM
emailAddress is what ServiceNow checks to authenticate. It has to be there on sys_user table and ofcourse your IDP. There is no such field as entity on sys_user table which is why ServiceNow will not be able to understand the SAML response.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-27-2016 08:43 AM
I was able to resolve it. Turns out that decoding needed another certificate. Adding it resolved the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-19-2017 12:08 AM
Make sure that default is true , I was facing the same issue, this has resolved my issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-24-2019 08:00 AM
Hi Latawaz,
iam too facing the same issue could you please elaborate the resolution process, so that i can resolve from my end.
Also please let me know step by step procedure to solve this issue.
Thanks ,
Krishna