As might be clear from the previous sections, OpenEdge cannot authenticate a user account name in all OpenEdge domains. And of those domains in which OpenEdge can authenticate users, some are restricted for use by SQL clients and database utilities, while others are available for user authentication in all OpenEdge database clients. The common requirements that allow OpenEdge to authenticate users in an OpenEdge domain define an authentication-enabled domain, regardless of which database client supports it.
Thus, an authentication-enabled domain is one where the domain is configured with:
An authentication system that is enabled for user authentication — The Enabled or Enable authentication toggle box (depending on the tool) is selected in the authentication system configuration.
An authentication system that has access to a source of valid user accounts — For a user-defined authentication system, as implemented by the configured ABL authentication callback.
The option to enable the domain for run-time access — The Domain Enabled or Enabled toggle box (depending on the tool) is selected in the domain configuration.
Given all domains with this definition:
The built-in, authentication-enabled domains support OpenEdge-performed user authentication anywhere user credentials can be specified for all database clients.
The user-defined, authentication-enabled domains support only those OpenEdge-performed user authentication operations that are available as ABL statements, functions, or methods.
An authentication system that is enabled for user authentication — The Enabled or Enable authentication toggle box (depending on the tool) is selected in the authentication system configuration.