Login Looping

[Gemma4]

When trying to log in to our dev instance, I am getting stuck in an endless reroute loop trying to login.

I have tried to clear my browser cookies and cache and get the same loop.
I have tried to log in using incognito mode and get the same loop.

Below is the address that I am attempting to use when I get the endless looping. 

https://instancename.service-now.com/login.do

This is the only address I can use to access dev,

https://instancename.service-now.com/login

glide.authentication.external.disable_local_login is set to true and tried to change it to false- looping either way

I have tried adding many addresses to our property glide.security.url.whitelist in case that was the issue, see below. 

First attempt
https://instancename.service-now.com,
https://instancename.service-now.com/logout_success.do,
https://instancename.service-now.com/sp?id=landing,
https://instancename.onelogin.com

2nd
https://instancename.onelogin.com,
https:/instancename.service-now.com/external_logout_complete.do

 3rd

https://instancename.service-now.com/sp/?id=landing
https://instancename.service-now.com/sp?id=landing
https://instancename.service-now.com/auth_redirect.do?sysparm_stack=no&sysparm_url=logout_success.do
https://instancename.service-now.com/logout_success.do

Has anyone else encountered this or have suggestions? 

Thanks

[Bert_c1]

Have you reported this to your instance admin? Can others log in to your instance? Or create a Support Case for your hosted instance.

[Gemma4]

Thanks @Bert_c1  I am the system admin and am having this issue; along with another admin. I've created a support case already and am still working with support to determine root cause.  I posted on the community to get feedback from others who might have also experienced this same issue.  Thanks for any feedback or suggestions you may have. 

[Stephanie Norto]

This was resolved by removing the value in the 'glide.authenticate.sso.redirect.idp' sys_properties. The value was no longer present in the instance

[mrmleczko]

having same problem now in January , if this is a normal solution can you direct us on accomplishing the removal ? just using developer tools and circumventing something that has a bug?