Iv. Oracle User Management (profile)

I. Using profile to manage user passwords
Overview: Profile is a collection of commands that are password-constrained and resource-constrained, and when a database is established, Oracle automatically establishes a profile called default. When the setup user does not specify the profile option, Oracle assigns default to the user.
1. Account Lockout
Overview: Specify the number of times a password can be entered when the account (user) logs on, or you can specify the time that the user is locked out (days) to execute the command as a DBA.
Example: Specify Scott this user can only try to log in at most 3 times, lockout time is 2 days, let us see how to implement.
Create profile file
Sql> Create profile Lock_account limit failed_login_attempts 3 password_lock_time 2;
sql> alter user Scott profile Lock_account;

2. Unlock the account (user)
sql> alter user Scott account unlock;

3. Terminating the password
In order for the user to periodically change the password can be done using the command to terminate the password, the same command also requires the role of the DBA to operate.
Example: Create a profile for the user test created earlier, requiring the user to modify his or her login password every 10 days with a grace period of 2 days. See how it's done.
Sql> Create profile Myprofile limit password_life_time Password_grace_time 2;
sql> alter user test profile Myprofile;

Second, password history
Overview: If you want users to be able to change passwords without using passwords that they have used before, you can use the password history so that Oracle will store the password modification information in the data dictionary so that when the user modifies the password, Oracle compares the old and new passwords, and when the old and new passwords are found, The user is prompted to reenter the password.
Example:
1) Establish profile
Sql>create profile Password_history limit password_life_time Password_grace_time 2
Password_reuse_time//password_reuse_time Specifies that the password can be reused for 10 days
2) assigned to a user
sql> alter user test profile password_history;

Third, delete profile
Overview: When you don't need a profile file, you can delete it.
Sql> Drop profile Password_history "Casade"
Note: After the file is deleted, all the users who use this file to bind are also released.
If you add Casade, you'll remove the cascade of related stuff.

Iv. Oracle User Management (profile)