Iv. Oracle User Management II

Overview of managing user passwords with Profiles: Profile is a collection of commands that are password-constrained, resource-constrained, and when a database is established, Oracle automatically establishes a form named 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 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 a profile SQL> CreateProfile Lock_account Limit failed_login_attempts3Password_lock_time2; SQL> Alter UserScott profile Lock_account;2. Unlock SQL for account (user)> Alter UserScott 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> CreateProfile Myprofile Limit Password_life_timeTenPassword_grace_time2; SQL> Alter Usertest profile Myprofile; Overview of password history: If you want users to change their passwords, you can use password history, so that Oracle will store the password modification information in the data dictionary, so that when the user changes the password, Oracle compares the old and new passwords and prompts the user to reenter the password when the old and new passwords are found. Example:1) Establish Profilesql>CreateProfile Password_history Limit Password_life_timeTenPassword_grace_time2Password_reuse_timeTen //password_reuse_time Specifies that passwords can be reused for 10 days after they are reused2) assigned to a user SQL> Alter Usertest profile password_history; Delete Profiles Overview: When you do not require a profile, you can delete the file. 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 related items as well.