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 SRC Mobile - Unable to login to server with SAML2 auth - authentication failed or Failed to Log in
Steps to Reproduce: 1 Try to log in to SAML2 environment Actual Results:
CMS-XML How to setup SBM to use CAC/PIV SmartCard Authentication
NOTE: To watch a video of these steps , see KB S141238 . For SBM 11.x, see KB S141650 .
CMS-XML How to setup SBM to use CAC/PIV SmartCard Authentication SBM 11
For SBM 11.2 and later use KB S142941 . NOTE: To watch a video of these steps , see KB S141238 .
CMS-XML Dim2009R2: SSO CAC: How to change Bind User password when SSO CAC is enabled for Dimensions authentication
security.credentials The ones which have Type="htf:encstring" need to be replaced with the string from step c. e. When done save the changes.
CMS-XML Dim2009R2: SSO CAC: Error authenticating user: Cannot initialize LDAP context or Invalid username or password
5. Once you have determined the LDAP creditionals, stop your various services, rename the dm.cfg file to LDAP_dm.cfg, revert the files saved in Step 1.
CMS-XML Electronic Signatures and CAC Authentication
Electronic Signatures and CAC Authentication
CMS-XML KM-Dim14: Microsoft Edge does not work with CAC authentication
KM-Dim14: Microsoft Edge does not work with CAC authentication
CMS-XML How to add identity transformer code to configuration.xml for CAC and PIV authentication.
How to add identity transformer code to configuration.xml for CAC and PIV authentication .
CMS-XML Cannot connect iOS SBM Mobile Client with saml2 /ADFS - Error: Authentication Failed
Cannot connect iOS SBM Mobile Client with saml 2 /ADFS - Error: Authentication Failed
CMS-XML SBM throws error intermittently when using SAML2 third party authentication
It is possible that SBM users can get a SAML 2 login error when configured to use third party authentication with SAML 2. This issue would have started occurring as of February 2020, and affects many IdP providers such as Okta and SecureAuth. This occurs because of changes in the way third party cookies are handled in by Chrome, Firefox and Edge. Specifically, the industry refers to this as SameSite cookie policy.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs