User registry considerations | HCL Digital Experience

A user registry or repository authenticates a user and retrieves information about users and groups to do security-related functions, including authentication and authorization.

User registries store user account information, such as user ID and password, that can be accessed during authentication. User repositories store user profiles and preference information. A user registry or repository is used to:
  • Authenticate a user by using basic authentication, identity assertion, or client certificates
  • Retrieve user and group information to do security-related administrative functions such as mapping users and groups to security roles
By default, HCL Digital Experience is installed with a federated repository with a built-in file repository. The federated repository allows you to add various user registries, realm support for Virtual Portals, and/or property extensions to create a single, working unit. The available user registries that you can add to the federated repository are LDAP user registries, database user registries, and custom user registries.
Remember: Using the built-in file repository is not recommended in a production environment. After you add another repository and choose the administrative users from that repository, you must remove the file repository.

Based on the federated repository, HCL Portal allows you to create a user base that can be federated over multiple repositories: LDAP, DB, and/or custom user registry. It also allows you to define additional attributes in a separate store if your corporate LDAP directory is read-only.

If you are using a federated repository, you must plan on where you want to store new users and groups. By default, new users and groups are stored in the default file repository. If you use multiple LDAP user registries and database user registries, you must figure out which user registry you want to define as your default user registry where new users and groups are stored. After you add all user registries to your federated repository, you can run the wp-set-entitytypes task to set a specific user registry as the default location.

Remember: Before you combine multiple user registries, review the registries for the following limitations and correct any issues:
  • Distinguished names must be unique for a realm over all registries. For example, if uid=wpsadmin,o=yourco exists in LDAP1, it must not exist in LDAP2, LDAP3, or DB1.
  • The short name, for example wpsadmin, should be unique for a realm over all registries.
  • The base distinguished names for all registries that are used within a realm must not overlap; for example, if LDAP1 is c=us,o=yourco, LDAP2 must not be o=yourco.
  • Do not leave the base entry blank for any of the registries used within a realm.
  • If IBM® Domino® is one of your user registries in a multiple registry configuration and shares a realm with another user registry, ensure that the groups are stored in a hierarchical format in the Domino® Directory as opposed to the default flat-naming structure. For example, the flat-naming convention is cn=groupName and the hierarchical format is cn=groupName,o=root.
  • The user must exist in a user registry and not within the property extension configuration; otherwise, the user cannot be a member of the realm.