Authentication is the process of verifying the identity of a user, device, or other entity in a computer system, often as a prerequisite to granting access to resources in a system.
Oracle provides several means for users to be authenticated before they are allowed to create a database session.
Database Authentication
Identified and authenticated by the database, which is called database authentication. If you choose database authentication for a user, then administration of the user account including authentication of that user is performed entirely by Oracle Database.
External Authentication
Authenticated by the operating system or network service, which is called external authentication.
When you choose external authentication for a user, the user account is maintained by Oracle Database, but password administration and user authentication is performed by an external service. This external service can be the operating system or a network service, such as Oracle Net.
Global Authentication & Authorization
Authenticated globally by Secure Sockets Layer (SSL), called global users, whose database access is through global roles, authorized by an enterprise directory.
Oracle Advanced Security enables you to centralize management of user-related information, including authorizations, in an LDAP-based directory service. Users can be identified in the database as global users, meaning that they are authenticated by SSL and that the management of these users is done outside of the database by the centralized directory service. Global roles are defined in a database and are known only to that database, but authorizations for such roles is done by the directory service.
Proxy Authentication & Authorization
Allowed to connect through a middle-tier server that authenticates the user, assumes that identity, and can enable specific roles for the user. This combination of actions and abilities is called proxy authentication and authorization.
It is possible to design a middle-tier server to proxy clients in a secure fashion.
Oracle provides several means for users to be authenticated before they are allowed to create a database session.
Database Authentication
Identified and authenticated by the database, which is called database authentication. If you choose database authentication for a user, then administration of the user account including authentication of that user is performed entirely by Oracle Database.
External Authentication
Authenticated by the operating system or network service, which is called external authentication.
When you choose external authentication for a user, the user account is maintained by Oracle Database, but password administration and user authentication is performed by an external service. This external service can be the operating system or a network service, such as Oracle Net.
Global Authentication & Authorization
Authenticated globally by Secure Sockets Layer (SSL), called global users, whose database access is through global roles, authorized by an enterprise directory.
Oracle Advanced Security enables you to centralize management of user-related information, including authorizations, in an LDAP-based directory service. Users can be identified in the database as global users, meaning that they are authenticated by SSL and that the management of these users is done outside of the database by the centralized directory service. Global roles are defined in a database and are known only to that database, but authorizations for such roles is done by the directory service.
Proxy Authentication & Authorization
Allowed to connect through a middle-tier server that authenticates the user, assumes that identity, and can enable specific roles for the user. This combination of actions and abilities is called proxy authentication and authorization.
It is possible to design a middle-tier server to proxy clients in a secure fashion.
Oracle provides three forms of proxy authentication:
|
The middle-tier server
authenticates itself with the database server and a client, in this case an application
user or another application, authenticates itself with the middle-tier
server. Client identities can be maintained all the way through to the
database.
|
The client, in this case
a database user, is not authenticated by the middle-tier server. The clients
identity and database password are passed through the middle-tier server to
the database server for authentication.
|
The client, in this case
a global user, is authenticated by the middle-tier server, and passes one of the
following through the middle tier for retrieving the client's user name.
|
Comments