After enabling SSO within SRA, the following error occurs when testing the connection within Jenkins: Circular redirect to 'http://myssoserver:8085/idp/login'
An HTTP 405 error is received when trying to login via SSO if the referer header is only a host name (ie "http://host/") which the SSO server uses as a "return" URL.
Starting in SBM 11.4.2, you can use SBM Configurator to allow selected SBM component servers and other hosts in the continue and wreply HTTP parameters used with SSO redirects . This enables you to define hosts that have SSO protected applications. When enabled, SSO will refuse to accept requests or redirect to hosts that are not on the list.
When accessing the Request Password Reset link on the login page, it redirect us to: "localhost:/tmtrack/tmtrack.dll?LoginPage&Template=loginreset which does not exist since the Dimensions CM SSO Server is being used.
When using SSO and http, if the user goes to http://server/tmtrack/tmtrack.dll, they will be redirected to https. However, users may be prompted and told that non-secure content is being used. As an example, the user may get this Security Warning
2. The Application Engine will initiate the SSO connection via the gatekeeper. The gatekeeper will then redirect the user to the federation server for authentication.
If you configure SBM to use beyond the firewall feature in the configurator then you should be able to access SBM via a published service outside of the domain. If you have SSO turned on and change the IIS port for the external host then this will not work as after the SSO authentication is complete it redirects back to the default IIS port.
