Find Answers

Filter Search Results
All Products:

Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML SRA removing LDAP authorization realm does not remove that realms groups and users from the DB
- When this is activated, it automatically imports a range of groups and matches any membership of those groups against the users defined in SRA Authentication Realms. It groups are removed, they are automatically re-imported.
CMS-XML When importing groups from LDAP roles assigned to the template user via groups are not assigned to the imported users
Expected result: - The role assignments of the TemplateUser (through Group A) should be assigned to the imported users (through Group A membership ) Actual result:
CMS-XML Group import from LDAP fails if seat licenses are not used on this SBM Server
When trying to import groups and users using the Import groups from LDAP feature on a SBM system that has no seat licenses, the import fails with the following error: ERROR: The number of Regular Users and Managed Administrators, xx, exceeds the number of User seat licenses, 0.
CMS-XML Group Attribute Sort Issues when applying long lists
The issue will be corrected in 12.7. Before that release, items in the group sub-group can be sorted manually, or additional sub-groups may be added to shorten the lists.
CMS-XML LDAP authentication is not working
Following the steps provided in the SRA 4.5.1 documentation we configured LDAP authentication. The user and group import is working fine, however when an LDAP user is trying to log in the get Invalid username or password.
CMS-XML Cannot edit LDAP scheduler job name
When you setup a scheduled LDAP job, the Name field for the job is read-only. This is a problem because there are several types of jobs (import users, import contacts, update users, and import groups ). When looking at the list of scheduled jobs, you cannot tell which LDAP job is which.
CMS-XML Group By fields is blank on User Synchronization screen
[Expected Results] Should be able to give the LDAP attribute (i.e. Department) that is used to organize the users into the correct Resource Team. [User Impact / Workaround Required]
CMS-XML MCLG: LDAP: Only want to see a few of the LDAP users, not all of them
In previous versions of Collage, you could set the LDAP Group Filter to narrow down the list of groups displayed on the System | Users and Groups | Groups screen. However, all of the users in the LDAP Root still showed on the User screen. Beginning in Collage, you can limit the list of users as well.
CMS-XML Failed login attempt with LDAP authentication causes two tries for each login.
If you have ldap authentication setup and attempt to login as one of the ldap users with a bad password then agile makes two attempts to connect and causes the users account to be locked out in Active Directory before the domain group policies limit. In other words if your group policy says accounts should be locked out after 3 failed attempts you will actually get locked out if you put in the wrong password in Agile just twice because it tries 2 times for each, so four tries with just two failed attempts.
CMS-XML Automatically Added Occasional Users from LDAP get Regular access type by default
Automatically Added Occasional Users from LDAP get Regular access type by default LDAP users should be created in SBM with occasional access type when you set the Default SBM User Group for new users to a group with occasional access type but users are being created with regular access type instead.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs