1. Oracle Communications Diameter Signaling Router Cloud Disaster Recovery Guide
  2. Resolving User Credential Issues after Database Restore

5 Resolving User Credential Issues after Database Restore

User incompatibilities may introduce security holes or prevent access to the network by administrators. Inconsistencies among users are not considered a threat to the database, however. Review each user difference carefully to ensure that the restoration will not impact security or accessibility.

5.1 Restoring a Deleted User

These users were removed prior to creation of the backup and archive file. They will be reintroduced by system restoration of that file.

Figure 5-1 Testuser


Testuser

5.2 Keeping a Restored user

Perform the following procedure to keep users that will be restored by system restoration:

Note:

If this procedure fails, contact My Oracle Support (MOS).
  1. Establish a GUI session on the NOAM server by using the VIP IP address of the NOAM server. Open the web browser and enter the following url http://<Primary_NOAM_VIP_IP_Address>.
  2. Navigate to Administration, Access Control, and then Users.
    1. Select the user and click Change Password.
    2. Enter a new password and click Continue.

5.3 Removing a Restored User

Perform the following procedure to remove users that will be restored by system restoration:

Note:

If this procedure fails, contact My Oracle Support (MOS).
  1. Establish a GUI session on the NOAM server by using the VIP IP address of the NOAM server. Open the web browser and enter the following url http://<Primary_NOAM_VIP_IP_Address>.
  2. After restoration delete user:
    1. Navigate to Administration, Access Control, and then Users.
    2. Select the user and click Delete.
    3. Click Ok to confirm.

5.4 Restoring a Modified User

Before the backup and archive files were created, the passwords for these users are changed.

Figure 5-2 Test user


Test user

Before Restoration:

Verify access to an user with administrator permissions. Contact every impacted user and let them know that their password will be changed while this maintenance is being done.

After Restoration:

All users in this category should log in and have their passwords reset. To reset a user's password, follow the instructions in My Oracle Support (MOS).

5.5 Restoring an Archive that does not contain a Current User

These users have been created after the creation of the backup and archive file. The user will be deleted by system restoration of that file.

Figure 5-3 Test user


Test user

If the user no longer exist, do not perform any additional steps. The user is permanently removed.

Perform the following procedure to remove users that will be restored by system restoration:

Note:

If this procedure fails, contact My Oracle Support (MOS).
  1. Notify affected users before restoration:
    1. Contact each user that is affected before the restoration and notify them that you will reset their password during this maintenance operation.
  2. Log in to the NOAM VIP:
    1. Establish a GUI session on the NOAM server by using the VIP IP address of the NOAM server. Open the web browser and enter the following url http://Primary_NOAM_VIP_IP_Address>.
  3. Navigate to Administration, Access Control, and then Users. Under each affected user, record the following:
    1. Username
    2. Account status
    3. Remote Auth
    4. Local Auth
    5. Concurrent Logins Allowed
    6. Inactivity Limit
    7. Comment
    8. Groups
  4. After restoration:
    1. Establish a GUI session on the NOAM server by using the VIP IP address of the NOAM server. Open the web browser and enter the following url http://<Primary_NOAM_VIP_IP_Address>.
  5. After Restoration recreate affected user and required group:
    1. Navigate to Administration, Access control, and then Users.
    2. Click Insert and recreate the user using the data collected in step 4 and click OK.
  6. Repeat step 5 to recreate additional users and groups.
  7. After restoration reset the passwords.