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 DimCM: SSO: LDAPS: Cannot initialize LDAP Context
DimCM: SSO: LDAPS : Cannot initialize LDAP Context
CMS-XML Dim2009R2: SSO CAC: Error authenticating user: Cannot initialize LDAP context or Invalid username or password
Dim2009R2: SSO CAC: Error authenticating user: Cannot initialize LDAP context or Invalid username or password
CMS-XML KM-Dim10: Reported Defect DEF87245: Issue Fixed in Dimensions 10.1.1: LDAP: When the base context for search is set to domain level users are unable to log into Dim with serach set to 0 or 1
KM-Dim10: Reported Defect DEF87245: Issue Fixed in Dimensions 10.1.1: LDAP : When the base context for search is set to domain level users are unable to log into Dim with serach set to 0 or 1
CMS-XML Non-standard UserNameAttribute in LDAPINFOFILE (pvcsldap.ini) overwritten if no changes are made to LDAP settings
The customer needed to authenticate users via their e-mail address instead of "cn" as the Base User Context , which is not available from the choice list in Configure Project. The pvcsldap.ini file can be hand-edited to make this work, but if LDAP settings are viewed after this point the file is overwritten, even if no changes are made This results in Version Manager being unable to authenticate users until the pvcsldap.ini file is hand-edited again.
MS-WORD PVCS 7.5.0.0 LDAP Training
Base User Context – This determines what level Version Manager will bind to the directory server. This is part of the query sent to the directory server.
CMS-XML KM-Dim9: LDAP Error: Invalid Credentials Error: User Authentication failed - LDAP bind to server failed
1. Obtain a copy of the Softerra LDAP browser and install. This is a free browser that is easy to use and fetarure the ability to query LDAP 3 compliant directory servers for all valid base context . Once configured and connected, the full distinguished name of the user can be determined.
CMS-XML ORA-01400 error when saving LDAP/SSO server configuration
If you are configuring for SSO authentication without LDAP authentication and leave the fields in the upper portion of the tab empty, you will receive an error from Oracle when you click OK. 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.
CMS-XML MCLG: 5.1.2.7 Hot fix: SSL for Contribution, LDAP SSL, paste from Word
An error like the following may also appear in the Collage log: WRN 2007/08/20 13:16:12 PDT-- Storage: Approve action on asset level not allowed in a task context ' Fixes from hot fix 5.1.2.6:
CMS-XML MCLG: Troubleshooting and configuration tips for setting up LDAP/Active Directory
If that still does not help, use the Softerra LDAP Browser described above to connect to the LDAP server. Be sure to use the same root context and user information as setup on the Collage LDAP Setup screen. If you cannot see the users and groups here, the LDAP user probably does not have permissions to view the LDAP tree or the LDAP Root was defined too low in the tree.
CMS-XML How to setup Dimensions CM, RM and other Serena products to utilize the SBM SSO using LDAP authentication model
Next, we need to modify the SBM Context Provider. Modify the same configuration.xml for the following line.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs