Admin account locked owing to wron password

[gnampoothiry]

Hi Guys,

How do we unlock an Admin acocunt in Tm1, once we have exceeded maximum number attempts for log in with wrong password?

Is there any way we can unlock the admin account or settings to increase the number of maximum attempts to logon with wrong password?

Thanks in Advance.

Regards,
Girish

[ScottW]

Solution varies depending on the TM1 version.

Some TM1 versions will unlock an account that has been locked due to maximum login attempts with wrong password being exceeded with a password reset. However, most versions of TM1 will only unlock an account that has been locked for this reason following a fresh restart of the server (server bounce).

Generally, TM1 will not allow you to delete a client then recreate a client with the same name during a session.

The default number of login attempts is 3. To override the default simple add the MaximumLoginAttempts parameter to the tm1s.cfg file in the database root directory.

Generally it would be considered bad practice to actually use the Admin account on a production system. (This account can't be deleted by the way.) Much better to assign specific users to the Admin group then you know who is doing what on the system, and depending on logging settings also have an audit trail of changes.

[gnampoothiry]

Thanks Scott.

Information was really helpful.

Regards,
Girish

[asutcliffe]

Solution varies depending on the TM1 version.

Some TM1 versions will unlock an account that has been locked due to maximum login attempts with wrong password being exceeded with a password reset. However, most versions of TM1 will only unlock an account that has been locked for this reason following a fresh restart of the server (server bounce).

Hmm, I'm on 9.4.1 SP3, can anyone tell me if server restart will automatically unlock accounts locked this way or will I have had to reset their password first?

Oh and I know it's bad practice now.

Cheers,
Alex

[asutcliffe]

To answer my own question, a server restart unlocked the account. I didn't have to reset the password first.