+

Search Tips   |   Advanced Search

User registry considerations

A user registry or repository authenticates a user and retrieves information about users and groups to do security-related functions, including 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:

By default, HCL Portal is installed with a federated repository with a built-in file-based repository. The federated repository allows us 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 we can add to the federated repository are LDAP user registries, database user registries, and custom user registries. Using the built-in file-based repository is not recommended in a production environment.

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

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


Combine multiple user registries

Limitations:

See: