glide.authenticate.sso.redirect.idp connection issue appears

[petterbj_rgmo]

Hello all,

I am working with a client where we have a on-premise ServiceNow solution. We have a load balancer in front of 3 nodes running ServiceNow application. We have created a SSO integration with ADFS 2.0.

To verify that the IDP record and ADFS is configured correctly we have tried to use the <instance>.service-now.com/login_with_sso.do?glode_sso_id=<sys_id_IDP>. This works just fine and we are authenticated to the ADFS.For automatically sending the users to authenticate to the IDP we are trying to add the following property: glide.authenticate.sso.redirect.idp, type: string, value: IDP sys_id. This has worked for clients which have a cloud based ServiceNow architecture. When we add the glide.authenticate.sso.redirect.idp property the connection to the application dies and we are kicked out of the instance. We are not able to access the IDP and authenticate after the system property has been added to the system. Has any one experienced something similar?   Is on premise ServiceNow working different from cloud-based ServiceNow?

Debugging this has been a nightmare as we do not have anything to go on. I can reach the instance with running ping from CMD, but when i try to hit the URL I get a message stating that the connection was not made.

Is this a connectivity issue, or is there something in ServiceNow that we are missing?

[Sarah]

I believe he meant glide.authenticate.sso.redirect.idp

[syedfarhan]

Have a look at this for more info : http://wiki.servicenow.com/index.php?title=SAML_2.0_Web_Browser_SSO_Profile#gsc.tab=0

it is for SAML2 security token with user info

[petterbj_rgmo]

As we are running ServiceNow on premise, this is an issue between a load balancer and the ADFS returning the SAML response. Some subsites are not handled by the load balancer. This does not seem to be a ServiceNow issue.