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
SRA: Jenkins Plugin: SSO: Circular redirect to 'http://myssoserver:8085/ idp/login ' error occurs
CMS-XML Error 500 after login using a http://hostname/workcenter/tmtrack.dll?shell=swc#1 URL after login
- enable Single Sign-On - in Security > Secure SSO > SSO URL Overrides override the Federation Server URL to https://hostname: 8243 / idp/login - Apply the change
CMS-XML Out of network users communicate with JBOSS on port 443
1. As of SBM 10.1.2, /AlfSSOLogin / will become / IDP/Login /.
CMS-XML Duplicate filter name [RemoteUserPrincipalFilter] in console log - users not able to log in using third party authentication (non SAML) in SBM 11.5
If the customer enables non SAML 3rd party authentication in Configurator, the users will see an error 404 from Tomcat stating that the / idp/login URL is not found. This is caused by the web.xml will contain 2 remote-user principal filters (because the SAML section also contains one) which will prevent third party authentication from working.
CMS-XML SRA: CommandLine: SSO: java.io.IOException: Error downloading the configuration from the server at http://:8080/serena_ra/cli/application.wadl due to CircularRedirectException
Caused by: org.apache.commons.httpclient.CircularRedirectException: Circular redirect to 'https://<servername>: 8243 / idp/login '
CMS-XML HTTP Status 404 – Not Found when enabling third party authentication
Message / idp/login Description
CMS-XML SDA gives error "SSO Gatekeeper error has occurred: Authentication processing error" with "Invalid federation server"
Invalid federation server URL: $HTTP_OR_HTTPS://$HOSTNAME:$PORT/ idp/login ?wa=wsignin1.0&wreply=http%3A%2F%2Fsoo4%3A8080%2Fserena_ra%2F&wctx=2%3A223680404&wct=2016-06-02T20%
CMS-XML How to setup RLM (Release Automation, SDA, SRA) to use SSO with SBM
<parameter name="SecurityTokenServiceExternal" Type="xsd:anyURI">http://sbm-server:sbm-port/idp/services/Trust</parameter> <parameter name="FederationServerURL" Type="xsd:anyURI">http://sbm-server:sbm-port/ idp/login </parameter>
CMS-XML Enable third party authentication with SSO
6. At this time, a header variable is also set to the users login id. 7. The user is redirected back to the Serena Federation Server. 8. The third party authenticator scans the header again, finds the token and lets the packet through to the Federation Server URL (HTTP://Servername:8085/ idp/login ).
CMS-XML Dim14: Installation: Upgrade: SSO: Gatekeeper-core-config.xml file has duplicate entries
<parameter Type="xsd:anyURI" name="FederationServerURL">https://DIMSERVER:8443/ idp/login </parameter> <parameter Type="xsd:anyURI" name="FederationServerURL">https://DIMSERVER:8443/idp/login</parameter>
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs