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
PDF Installation Guide and Configuration Guide
5. Enter the Custom HTTP header that is used by the identity provider to pass the user ID to SBM. The default value is REMOTE_USER .
PDF Installation Guide and Configuration Guide
REMOTE_USER . 5. If you are using External Identity Provider authentication with Single Sign-On, select the Configure custom authentication filter check box to enter your own custom filter for the external identity provider. For example:
PDF Installation Guide and Configuration Guide
Otherwise, if you are not using SSO, enter the Custom HTTP header that is used by the identity provider to pass the user ID to SBM. The default value is REMOTE_USER .
PDF Installation Guide and Configuration Guide
4. On the External Identity Provider tab, enter the Custom HTTP header that is used by the identity provider to pass the user ID to SBM. The default value is REMOTE_USER .
CMS-XML KM-Dim10: Reported Defect DEF106238: Web client does not remember remote login user and password settings
KM-Dim10: Reported Defect DEF106238: Web client does not remember remote login user and password settings
CMS-XML Dim2009R2: Remote deployment: User's account is disabled please contact your administrator.
Deployment to HPUX remote node user facing below error message
CMS-XML KM-Dim9: How to set up replication with a different user id on remote server
1. Add remote replicator user id in dm.cfg on the master site. The parameter is as follows:
CMS-XML DimCM: Item Library Access and Credential Sets
There have been a number of enhancements to item library access in Dimensions CM so that the command of DPL (Define Product Library) accepts the /CREDENTIAL_SET parameter both for /ADD and /UPDATE. Along with this it is now possible to "secure" a Dimensions CM server/agent hosting item libraries. The remote node user and password selections have been removed.
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 HTTP Status 404 – Not Found when enabling third party authentication
<param-name>RemoteUserHeader</param-name> <param-value> remote-user </param-value> </init-param>
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs