Registering external users with Profiles
Ensure that external users are recognized by populating them in the Profiles database via IBM Tivoli Directory Integrator.
The Profiles database must be enabled as the user directory, and all users must be stored in the Profiles database. If the setting...
profiles_directory_service_extension_enabled
...is set to true in LotusConnections-config.xml, then the Profiles database is the user directory. This is enabled by default.
External users must be populated into the organization's LDAP before they can be populated into Profiles.
Tivoli Directory Integrator synchronizes information between the Profiles database, and the LDAP directory. In Tivoli Directory Integrator a member is considered either internal or external. An internal member is often referred to as an employee, and belongs to the organization. An external member is often referred to as a visitor, and is a person who is not part of the organization but can access some of the organization's content.
Once you register a user as either internal or external, we cannot change it. If we update an external user so they are registered as internal, then delete the external user and re-create that user as an internal user.
If we update Tivoli Directory Integrator to enable external users, then by default the string - External User is appended to the display name of an external user. This string makes it possible to identify which users are external users, and can be customized.
There are three ways to register a user. All methods set the value of mode to external to denote an external user.
- Map a standard LDAP attribute for external users
- Map a standard LDAP attribute using JavaScript
- Use an LDAP branch to store external users
Parent topic:
Manage external user access
Related:
Configure External Collaboration
Map fields
Use the Profiles database as the user directory
Example complex mapping of Profiles data
Configure the Manager designation in user profiles