Find Answers

Filter Search Results
All Products:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML LDAP and SSO: When the SearchBase of an LDAP look up of Active Directory Server is set to the root of the tree, it is possible to get PartialResultException - Error processing LDAP search result(s): null
When the SearchBase of an LDAP look up of Active Directory Server is set to the root of the tree for LDAP and SSO then authentication does not work. If you have "referrals" selected then you get the following error in sso - idp.log : Example error:
CMS-XML SmartCard (CAC) authentication from VM desktop clients to an SBM SSO server breaks after upgrading to SBM 11.4
This error corresponds with the following entry getting added to SBM's sso - idp.log file:
CMS-XML SSO with Windows Authentication checks for the existence of loginid with the domain stripped it
SSO - IDP.LOG returns "org.eclipse.higgins.idas.api.IdASException:" in web services. Work Around
CMS-XML SAML2 setup fails with error "Unable to builder artifact for message to relying party"
After setting SBM SAML2 login, the user is unable to login. The sso - idp.log would show the stack trace[1] below. [1] Stack Trace2021-03-22 10:27:32,150 ERROR f: g: SBMSAMLEntryPoint.commence(123): Error processing metadata (EDQHM5HQNV75C6HJ): Unable to builder artifact for message to relying party
CMS-XML SBM remembers SmartCard login at login form
Now, try to login as username / password. The form login will fail because the smart card certificate was selected when prompted. Reviewing the sso - idp.log , you will see that the user that is check is the smart card user not the login form user.
CMS-XML Null Pointer Exception Error in RemoteUserFilter when turning on TRACE log level
we get an NPE and server is unusable. The SSO - IDP.LOG file may show something like this.
CMS-XML All communication from Tomcat to IIS fails if Client Certificate Authentication is enabled
In the sso - idp.log file, a connection reset error appears:
CMS-XML ALF SSO Gatekeeper error has occurred: Error obtaining security token. Validation of WS-Federation token failed with code 40:Token issuer not allowed.
ALF SSO Gatekeeper error has occurred: Error obtaining security token. Validation of WS-Federation token failed with code 40:Token issuer not allowed.
CMS-XML Configurator does not allow for setting up SSO for external identity provider while using non-SSO auth on local server
Configurator removes the "custom HTTP header" or "remoteuserheader" setting from the web.xml whenever the authentication is changed (even with the "override authentication settings for this server" checked) away from the external identity provider with SSO . This prevents the setup of SSO using an external identity provider being used while using a non-SSO form of authentication on the local JBoss server where SSO is installed without manually modifying the web.xml file.
CMS-XML non-ASCII "allow search" fields do not work correctly - SSO errors
For a searchable field, enter a non-ASCII string, such as "Системная". If you have SSO enabled, this will change the search field to "searching" and the query never returns.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs