Welcome to the Connections Product Ideas Lab! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by the Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events, please visit our Connections page.

On-Prem: When changing LDAPs, there are no commands to resync Groups that are added to Communities, Files, Wikis & Activities.

When a user's external DIRECTORY_ID (i.e. LDAP ID/GUID) is changed (either by their LDAP record being moved or deleted/recreated), the admin can resync Profiles using TDI.

And then there are wsadmin ("Lifecycle") commands to re-sync the user's records for the membership tables in the other databases:

However, Connections does not have way to update DIRECTORY_ID of a group in the DB tables for the applications where it's possible to add Groups:
FILES, WIKIS, SNCOMM (Communities) and OPNACT (Activities).

Instead, customers have to directly update database of each component and update group's directory_id, or remove the group as member and re-add the group back in all applications which support groups.

wsadmin commands that can update DIRECTORY_ID of groups. This could possibly be done by using the CN attribute for the Groups as the input parameter.

Provide complete Support for LDAP changes for Groups.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 10 2018
  • Under review
  • Attach files