Professional Documents
Culture Documents
06 Alter User
06 Alter User
http://docs.oracle.com/cd/B12037_01/server.101/b10759/statements_4003.htm#sth
ref4149
Purpose
Use the ALTER USER statement:
To change the authentication or database resource characteristics of a database
user
To permit a proxy server to connect as a client without authentication
Prerequisites
You must have the ALTER USER system privilege. However, you can change your own
password without this privilege.
Syntax
alter_user::=
proxy_clause::=
proxy_authentication::=( proxy_clause)
Semantics
The keywords, parameters, and clauses described in this section are unique
to ALTER USER or have different semantics than they have in CREATE USER. Keywords,
parameters, and clauses that do not appear here have the same meaning as in
the CREATE USER statement.
IDENTIFIED Clause
Note:
Oracle Database expects a different timestamp for each resetting of a particular
password. If you reset one password multiple times within one second (for example,
by cycling through a set of passwords using a script), then the database may return an
error message that the password cannot be reused. For this reason, Oracle
recommends that you avoid using scripts to reset passwords.
You can omit the REPLACE clause if you are setting your own password for the first
time or you have the ALTER USER system privilege and you are changing another user's
password. However, unless you have the ALTER USER system privilege, you must
always specify the REPLACE clause if a password complexity verification function has
been enabled, either by running the UTLPWDMG.SQL script or by specifying such a
function in the PASSWORD_VERIFY_FUNCTION parameter of a profile that has been
assigned to the user.
Oracle Database does not check the old password, even if you provide it in
the REPLACE clause, unless you are changing your own existing password. If such a
check is important in other cases (for example, when a privileged user changes
another user's password), then ensure that the password complexity verification
function prohibits password changes in which the old password is null, or use
the OCIPasswordChange() call instead of ALTER USER.
Specify GLOBALLY AS 'external_name' to indicate that the user must be authenticated by
way of an LDAP V3 compliant directory service such as Oracle Internet Directory.
The proxy_clause lets you control the ability of a proxy (an application or application
server) to connect as the specified database or enterprise user and to activate all, some,
or none of the user's roles.
The proxy_clause provides several varieties of proxy authentication of database and
enterprise users. For information on proxy authentication of application users,
GRANT | REVOKE
Specify GRANT to allow the connection. Specify REVOKE to prohibit the connection.
CONNECT THROUGH Clause
Identify the proxy connecting to Oracle Database. Oracle Database expects the proxy
to authenticate the user unless you specify the AUTHENTICATED USING clause.
WITH ROLE
permits the proxy to connect as the specified user and to activate
only the roles that are specified by role_name.
WITH ROLE role_name
WITH NO ROLES
permits the proxy to connect as the specified user, but prohibits the
proxy from activating any of that user's roles after connecting.
If you do not specify any of these WITH clauses, then Oracle Database activates all
roles granted to the specified user automatically.
WITH NO ROLES
proxy_authentication
Use this clause to indicate how you want the proxy authenticated. This clause is valid
only as part of the GRANT CONNECT THROUGH proxy clause
(not REVOKE CONNECT THROUGH proxy).
AUTHENTICATION REQUIRED Clause
Specify AUTHENTICATION REQUIRED to ensure that authentication credentials for the user
must be presented when the user is authenticated through the specified proxy. The
credential is a password.
AUTHENTICATED USING
This clause has been deprecated and is ignored if you use it in your code. Oracle
recommends that you specify the proxy clause either with or without
the AUTHENTICATION REQUIRED clause.
Examples
Changing User Identification: Example
The following statement changes the password of the user sidney (created
in "Creating a Database User: Example") second_2nd_pwd and default tablespace to the
tablespace example:
ALTER USER sidney
IDENTIFIED BY second_2nd_pwd
DEFAULT TABLESPACE example;
At the beginning of sh's next session, Oracle Database enables all roles granted
directly to sh except the dw_manager role.
Changing User Authentication: Examples
The following statement changes the authentication mechanism of
user app_user1 (created in "Creating a Database User: Example"):
ALTER USER app_user1 IDENTIFIED GLOBALLY AS 'CN=tom,O=oracle,C=US';
If you cause a database user's password to expire with PASSWORD EXPIRE, then the user
(or the DBA) must change the password before attempting to log in to the database
following the expiration. However, tools such as SQL*Plus allow the user to change
the password on the first attempted login following the expiration.
Assigning a Tablespace Group: Example
The following statement assigns tbs_grp_01 (created in "Adding a Temporary
Tablespace to a Tablespace Group: Example") as the tablespace group for user sh:
ALTER USER sh
TEMPORARY TABLESPACE tbs_grp_01;
To show basic syntax, this example uses the sample database Sales History user ( sh)
as the proxy. Normally a proxy user would be an application server or middle-tier
entity. For information on creating the interface between an application user and a
database by way of an application server, please refer to Oracle Call Interface
Programmer's Guide.
The following statement takes away the right of user app_user1 to connect through the
proxy user sh:
ALTER USER app_user1 REVOKE CONNECT THROUGH sh;