Try OpenEdge Now
skip to main content
Identity Management
Configuring and Implementing Authentication in OpenEdge : Defining and configuring security domains : Pre-configured and reserved OpenEdge domains
 

Pre-configured and reserved OpenEdge domains

OpenEdge pre-configures several built-in domains in every OpenEdge RDBMS that you cannot remove. These built-in domains include the following:
*Default (blank) domain - This domain is initially configured with the _oeusertable authentication system. You can configure it with any available authentication system, including a user-defined one. However, you cannot remove the default domain from the OpenEdge database, and you cannot change its domain name or tenant name ("Default"). It is provided for backward compatibility with earlier releases where users are not defined as members of a domain. So, if you migrate an application to OpenEdge 11 from an earlier release that does not define domains, in OpenEdge 11, all users of the application are now defined as members of the default domain. In this case, users can identify themselves using a non-qualified user ID (see Specifying a user ID for OpenEdge authentication.
*WINDOWS and UNIX - These two domains are configured with the _oslocal authentication system and are enabled for user authentication operations against user accounts managed by the current operating system. You cannot change the configuration of these domains or remove them. OpenEdge reserves them for access to the database command-line utilities (_dbutil executables). These domains are not supported for use in an ABL application.
*WINDOWSID and UNIXID - These two domains are configured with the _oslocal authentication system and are enabled for SSO operations on the operating system process user ID. You cannot change the configuration of these domains or remove them. OpenEdge reserves these domains primarily for access to the database command-line utilities (_dbutil executables) when a database is not in an open and recovered state and the user's already authenticated operating system user identity must be used to access the database. For an ABL application, OpenEdge also assigns one of these domains for any user who connects a database without authenticating a user identity and is thus assigned the default OS process user ID as their connection identity.