OracleSecurity & users
Password profile settings
Password rules for each profile: lifetime, reuse, failed attempts and the verify function. Shows why an account locked or expired.
Not yet verified. How scripts are tested
1CLEAR COLUMNS2SET LINESIZE 100 PAGESIZE 200 TRIMOUT ON TAB OFF3COLUMN profile FORMAT A254COLUMN resource_name HEADING "SETTING" FORMAT A305COLUMN limit FORMAT A306 7SELECT profile, resource_name, limit8FROM dba_profiles9WHERE resource_type = 'PASSWORD'10ORDER BY profile, resource_name;Save it as ora-profiles.sql and run it with SQL> @ora-profiles.
Helps with
- ORA-28000: the account is locked
- ORA-28001: the password has expired
- ORA-28002: the password will expire within %s days
More Oracle scripts: Security & users
- Accounts locked, expired or expiring soonApplication accounts that aren't OPEN, or whose passwords expire in the next 14 days. Catch service accounts before they break an application.
- Who has DBA, SYSDBA and powerful system privilegesNon-Oracle accounts and roles holding the DBA role or high-risk ANY privileges, then everyone in the password file. Worth reviewing every audit cycle.
- CMU step 1: prepare Active DirectoryDone once by an AD administrator before any database work: create the service account the database binds with, install Oracle's password filter on…
- CMU step 2: export the AD root certificateThe database talks to AD over LDAPS, so its wallet must trust the certificate authority that issued the domain controllers' certificates. Export that…
- CMU step 3: create the walletBuilds the auto-login wallet the database reads at login: the service account's user name, DN and password, plus the AD root certificate. With PDBs,…
- CMU step 4: create dsi.oraTells the database which domain controllers to use. Put it in the same folder as the wallet from step 3. Use fully qualified host names, and list at…