You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

SSO not working after upgrade, Is something changed in "SSO for CP" between Feb 2016 and Aug 2017..

Received Response
15
Views
3
Comments
edited Jun 20, 2018 9:28AM in General Functional Discussions 3 comments

Content

We are observing that after redirection from our identity provider(Ping Federate) request reaches RNow however we are receiving response code 403-Forbidden when it tries to access page mentioned in CP_HOME_URL configuration setting. Moreover we observed that irrespective of whatever page we set as home page response remains the same i.e. - 403. 
Above issue is only on upgrade site(ver: Aug 2017). SSO integration with ping federate works fine on older version(ver: Feb 2016) 

It seems cp_profile cookie is not getting created on browser after redirection from Identity provider. Is something changed in "SSO for CP" between Feb 2016 and Aug 2017 versions

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!