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 SBM SSO login to Pulse may fail with mixed case usernames
SBM SSO login to Pulse may fail with mixed case usernames
CMS-XML Configurator gets null pointer exception after setting SSO LDAP then internal authentication
Configurator gets null pointer exception after setting SSO LDAP then internal authentication
CMS-XML Internal + SSO authentication doesn't time-out users after user session time-out
Internal + SSO authentication doesn't time-out users after user session time-out
CMS-XML SBM internal authentication from web services does not work if server is set to use NTCR / SSO authentication
SBM internal authentication from web services does not work if server is set to use NTCR / SSO authentication
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 SSO configuration of SSOLDAPThenInternal fails after upgrade to 11.6.1
When system is configured with SSO with SSO LDAP Then Internal , Configurator uses a compound authenticator. A regression was introduced in 11.6.1 where the parsing of AE authenticator throws a NullPointerException (NPE) and prevents the IdP from being initialized properly. No workaround can be provided besides turning off SSO.
CMS-XML SSO: LDAP: Use the Compound Authenticator to authenticate against one or more authenticators
Step 1: SSO must be enabled In SBM Configurator, go under Authentication > General tab.
CMS-XML How to setup SSO to validate users with LDAP, instead of SBM Application Engine validating the users with LDAP
To setup SSO to directly authenticate ... On the SSO server, edit ... ... to check the internal SBM passwords if ... On the Single Sign-On view, verify that Enable Single Sign-On is checked. Even if SSO was already checked ... To setup SSO to directly authenticate ... LDAP then check Internal Passwords, follow ... ... AE Authenticator for internal SBM passwords - ... Wrap the Compound Authenticator code around ... !-- Compound Authenticator -- ... ... string"> Compound </Setting ... ... -- End Compound Authenticator -- ... After the Compound Authenticator is added ...
CMS-XML IIS 6 Settings Cause Issues for SSO
If Single Sign On setup is having issues (no login page, "service unavailable" or internal error messages), it could be due to default settings used for Application Pools. The Business Mashups installer does not clear the option to Recycle Worker Processes in the Default Application Pool that is assigned to the tmtrack virtual directory. If this setting is not cleared, IIS will periodically restart.
CMS-XML "Premature end of file" error in sso-idp.log or mashupmgr.log
You may see the following error in either the sso-idp.log or the mashupmgr.log file when something is preventing access to the internal web services url.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs