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 Web Services "[URL_TO_GSOAP sbminternalservices72]" returned an error
When some users attempt to login via SSO, they receive the following error: Web Services "[URL_TO_GSOAP sbminternalservices72]" returned an error: "java.lang.illegalArumentException". The SSO - IDP.log shows the same error.
CMS-XML DIM RM: ALF SSO Gatekeeper error has occured: Error obtaining security token.
Detail Validation of occurred-Federation token failed with code 40:Token issuer not allowed . This message indicates that you may need to update the SSO STS certificate from SBM into the Dimension RM side.
CMS-XML SSO protected hosts - 403 Error – Forbidden
When this feature is activated in the SBM configurator, the RM server must be added to the “Select additional hosts that are allowed for SSO ”. If this RM server is NOT added, the message "403 Error – Forbidden
CMS-XML ORA-01400 error when saving LDAP/SSO server configuration
To get around this issue, enter your user name or some other text into both the “Base User Context” and “User Naming Attribute” fields. This will satisfy what Oracle is expecting and allow you to complete the section so you can auto-create new users. Error messages:
CMS-XML How to setup Dimensions CM, RM and other Serena products to utilize the SBM SSO using LDAP authentication model
If the user exists in the client requesting authentication, the user will be logged in, otherwise a login failure will occur. For example, if I go to the Dimensions CM website, I will be redirected to the SBM SSO Engine where my login can be authenticated via LDAP. Finally, I will be returned to the calling product (application) with an authenticated token where my username will be mapped to the product's internal user database; if the username does not exist, login will not be granted .
CMS-XML Dim CM/RM: SSO Gatekeeper error has occurred: Authentication processing error.
As part of the RM installation the file Common Tools\tomcat\6.0\conf\web.xml had been replaced. On examining the file it was found that the section "Serena SSO Gatekeeper Filter Configuration" was enabled. Commenting this out and restarting Tomcat allowed the tools to work again.
CMS-XML DIM RM: How to change the SSO provider hostname
DIM RM: How to change the SSO provider hostname
CMS-XML "Request is expired." received when attempting to login via SSO
"Request is expired." received when attempting to login via SSO
CMS-XML SSO: LDAP: Use the Compound Authenticator to authenticate against one or more authenticators
SSO : LDAP: Use the Compound Authenticator to authenticate against one or more authenticators
CMS-XML RQM REST services do not work with SSO
RQM REST services do not work with SSO
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs