Yeah, we're working on our 6.3 upgrade and SSO isn't functional, and we have no ability to debug why. Very, very frustrating.
Right, 6.3 doesn't appear to break SSO itself, but I heavily rely on this page for testing/confirming it.
In order to access this end point, two things must be in place. First, the role that is accessing this end point must have the following capability:
enableWebDebug = true|false
- Controls the visibility of the debug endpoints (i.e., /debug/splat).
- Defaults to false
If you browse to http://localhost:8000/en-US/info/ you will find the Development Services page where it will describe this new access requirement.
It is my understanding that this change was introduced for security purposes.
This worked, thank you!
Updating enableWebDebug = true in web.conf is all that is needed to expose the /debug/sso and /debug/echo endpoints, and updating the role with the webdebug capability in authorize.conf only applies to some of the debug endpoints (e.g. /debug/refresh and /bump, according to the info page that you cited).