OpenEdge provides two registry options to serve as the trusted domain registry in an ABL application:
Local database domain registry — The default domain registry used to authenticate or validate the user identity for a database connection. OpenEdge automatically creates a local database domain registry from the domains that are configured and enabled for use in the OpenEdge database when the database server (or client for a self-service database) starts up. Operations to manage the identity for all connections to this database use this local domain registry unless a database option is set to use the ABL session (application) domain registry instead.
ABL session domain registry — The domain registry used to authenticate or validate the user identity for an ABL session. This registry can also be used to authenticate or validate the identity for an existing database connection when a database option is set to use the application domain registry instead of the local database registry. For an ABL session, there is no default session domain registry. Your application must always build the session registry at run time using appropriate ABL mechanisms before it performs any identity management operations on the ABL session.
For basic information on configuring domains and domain registries in OpenEdge, see OpenEdge Getting Started: Identity Management. The following section describes the ABL features for building and using an ABL session domain registry.
Local database domain registry — The default domain registry used to authenticate or validate the user identity for a database connection. OpenEdge automatically creates a local database domain registry from the domains that are configured and enabled for use in the OpenEdge database when the database server (or client for a self-service database) starts up. Operations to manage the identity for all connections to this database use this local domain registry unless a database option is set to use the ABL session (application) domain registry instead.