Automatic access


When a user logs on to a product or solution for the first time, the product looks in the SECURITY data set for an existing record that matches the user ID for that user.

If no security record exists, the product uses the 9DEFAULT security record to grant access to the product, the product reports, and Db2. No security record is automatically created for the user ID, but as long as a 9DEFAULT record is available, the product uses it. If there is no security record for the user ID and no 9DEFAULT record, access is denied.

If the product finds a security record for the user ID or a 9DEFAULT record, the products looks in the PROFILE data set for a user record for that user ID. If no user record exists, the product creates one that uses the defaults in the 9DEFAULT record. If no 9DEFAULT record exists, the product creates a user record using internal defaults.


Warning

Important

When a user record is created, a User Profile exists for that user. Until an administrator modifies that User Profile, an individual security record is not created and the 9DEFAULT security record is used for access. If the 9DEFAULT security record is deleted, users without individual security records can no longer access the product. As long as the unmodified 9DEFAULT record exists in the SECURITY data set, the product grants access to all users to products.

The 9DEFAULT records shipped in the SECURITY, and PROFILE data sets contain default values that grant maximum authority to users. If you want to use the 9DEFAULT records but do not want all users to have maximum authority, perform one of the following tasks:

  • Modify the 9DEFAULT records before users access the product.
  • Delete the 9DEFAULT records to prevent unauthorized access.

In either case, first create a User Profile with maximum authority for yourself.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Common Db2 documents 13.1