Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML SRA: Jenkins Plugin: SSO: Circular redirect to 'http://myssoserver:8085/idp/login' error occurs
After enabling SSO within SRA, the following error occurs when testing the connection within Jenkins: Circular redirect to 'http://myssoserver:8085/idp/login'
CMS-XML HTTP 405 error from IIS on SSO login redirect
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.
CMS-XML SSO Gatekeeper error has occurred: Authentication processing error. Detail Error redirecting to federation services: maximum allowable URL length exceeded
SSO Gatekeeper error has occurred: Authentication processing error. Detail Error redirecting to federation services: maximum allowable URL length exceeded
CMS-XML Configuring SSO Protected Hosts
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.
CMS-XML DimCM: SSO: How to change the Request Pasword Reset link
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.
CMS-XML SSO and SSL: Only secure content is displayed and users get error about mixed content
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
CMS-XML Dim14: SSO CAC: Log Out button does not work as expected
Prerequisite: Before starting, you will need to determine what url you wish to have the users redirected to. Here's what you will want to do:
CMS-XML Dim2009R2: SSO CAC: Web Client and Admin Console provide a 404 Page not found error when using SBM SSO Server
The above error occurs because the redirect port in the fedsrv-core-config.xml file is set to default (8080). The current workaround is as follows: 1)
CMS-XML Enable third party authentication with SSO
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.
CMS-XML Beyond firewall does not work for IIS if SSO and port changed
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.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs