
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-17-2017 11:50 PM
Hello community,
We had SSO Setup with Azure in our sub-prod environment.
Everything was working well.
We ran a clone over the weekend, and it now redirects to SSOCircle.
I was under the impression that all SSO related config was kept after a clone.
The IDP that we setup has been preserved, and is set as default, yet it always redirects here.
Has anyone else encountered this?
Any easy way to fix without starting from scratch again?
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022
Solved! Go to Solution.
- Labels:
-
Integrations
- 5,509 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-18-2017 04:08 PM
OK.
So I fixed this issue by literally turning it on and off again.
-_-
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-28-2020 08:38 AM
How were you able to get into the properties with the redirect to the SSO Circle page?
Thanks,
Heather
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-09-2020 10:29 AM
Awesome its working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-23-2020 04:35 PM
Thank you for sharing. I've just had this issue occur after a clone of our test environment. The issue did not occur in our development environment just a week earlier.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-26-2020 12:12 PM
For the record, the accepted solution to this problem still works for Orlando Patch 2. My org just had this happen over the weekend.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-20-2020 05:29 PM
Thanks for this nifty fix. We have never had this issue before and we use PING. Just did clone of Prod (Orlando Patch 5) to QA instance and SSO did not work. After verifying setup was ready log case until i found this. Makes no sense but it worked.