Resetting MASTERADMIN Password in MSSQL and Oracle Databases for Advanced Authentication

Products

• CA Strong Authentication
• CA Advanced Authentication
• CA Risk Authentication

Issue/Introduction

This article provides SQL scripts for resetting the MASTERADMIN password in both MSSQL and Oracle database environments. By utilizing the provided SQL scripts for MSSQL and Oracle databases, administrators can easily reset the MASTERADMIN password.

Please note that these scripts assume you have the necessary privileges to modify the relevant tables.

Environment

Release :  9.1

Advanced Authentication

Resolution

Instructions:

• Ensure you have the necessary privileges to execute the provided SQL scripts.
• For the MSSQL script, replace <database_name> with the name of your target database.
• Copy the appropriate SQL script based on your database type (MSSQL or Oracle).
• Open a database management tool or command-line interface (CLI) and connect to your database server.
• Execute the SQL script against the respective database.
• Verify the changes by checking the updated values in the relevant tables.

 

Below are the scripts to reset the MASTERADMIN password based on your DB type:

SQL script for MSSQL DB Sever 

USE <database_name>;

UPDATE ARADMINBASICAUTHUSER
SET STRIKECOUNT = 0,
    PASSWORD = 'qTUh9O+l3xrahcLO9syibdgn2GY=:aB8KhgrRFuBIfvJXyevd+w+k4Wc=',
    PASSWDRESETTIME =  GETUTCDATE()
WHERE
    USERID = 'MASTERADMIN' AND
    ORGNAME = 'MASTERADMIN';
    
UPDATE ARADMINUSER
SET AUTHSTATUS = 'UPDATE'
WHERE ADMINID = 'MASTERADMIN' AND
ORGNAME = 'MASTERADMIN';

GO

SQL script for ORACLE DB Sever

UPDATE ARADMINBASICAUTHUSER
SET STRIKECOUNT = 0,
    PASSWORD = 'qTUh9O+l3xrahcLO9syibdgn2GY=:aB8KhgrRFuBIfvJXyevd+w+k4Wc=',
    PASSWDRESETTIME =  SYS_EXTRACT_UTC(CURRENT_TIMESTAMP)
WHERE
    USERID = 'MASTERADMIN' AND
    ORGNAME = 'MASTERADMIN';
    
UPDATE ARADMINUSER
SET AUTHSTATUS = 'UPDATE'
WHERE ADMINID = 'MASTERADMIN' AND
ORGNAME = 'MASTERADMIN';

COMMIT;

 

Note:

• It is crucial to exercise caution when executing scripts in a production environment.
• Please plan and test the process thoroughly in a non-production environment.
• Ensure you have a backup of your database before making any modifications.
• If you encounter any issues or have questions, consult with your database administrator or contact our support team for further assistance.