Reset MAXADMIN's password

Before you begin: this recovery procedure updates the Maximo database directly. Take a backup, confirm the database platform, follow your organisation's change process and test the update in a non-production environment first.

Use this procedure when a Maximo environment uses native authentication and you can no longer sign in as MAXADMIN. This commonly happens after refreshing a development environment from production, or when responsibility for an environment changes and the existing password is unavailable.

The statements below reset MAXADMIN to Password#1. They also set forceexpiration to 1, which makes Maximo ask for a new password at the next login.

The password is stored as hexadecimal data. Oracle, DB2 and SQL Server each use different syntax for representing that value, so select the statement for your database platform.

Oracle

--Update the Maximo Administrator Password to Password#1 & force Password change on next login
UPDATE
  MAXUSER
SET
  PASSWORD = '32EADE0476E145253F31C2002DFA7F3E4B9902366B8E08F1',
  FORCEEXPIRATION = 1
WHERE
  USERID = 'MAXADMIN';

DB2

DB2 uses the x'...' notation to identify the value as hexadecimal data.

--Update the Maximo Administrator Password to Password#1 & force Password change on next login
UPDATE
  MAXUSER
SET
  PASSWORD = x'32EADE0476E145253F31C2002DFA7F3E4B9902366B8E08F1',
  FORCEEXPIRATION = 1
WHERE
  USERID = 'MAXADMIN';

SQL Server

SQL Server uses the 0x... notation for hexadecimal data, without quotation marks around the value.

--Update the Maximo Administrator Password to Password#1 & force Password change on next login
UPDATE
  MAXUSER
SET
  PASSWORD = 0x32EADE0476E145253F31C2002DFA7F3E4B9902366B8E08F1,
  FORCEEXPIRATION = 1
WHERE
  USERID = 'MAXADMIN';

After the update

Commit the transaction if your database client does not do so automatically. Sign in as MAXADMIN with Password#1, then replace it when Maximo prompts you to choose a new password.

You can omit the forceexpiration assignment if you do not want Maximo to request an immediate password change. Keeping it enabled limits how long the shared recovery password remains valid.

This procedure applies to Maximo native authentication in versions 7.5.x through 7.6.x. Environments using LDAP, SAML or another external identity provider require the password to be recovered through that provider instead.