You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, TM1py checks first if the "password" is encoded, then if it fails to login with the password decoded, it tries with the password as it is. It means that if you have a wrong password, TM1py is going to use 2 failed attempts instead of just 1. This can lead to reaching the maximum of attempts very quickly and locked our Admin user.
To avoid this we could add a new parameter in the config.ini, called "password64" or if we want to make it less obvious it could be "pwd", the new parameter will be used to put the encoded password. TM1py could check first if there is a value for this new parameter then it tries to connect, if there is no value, TM1py will get the password from the parameter "password".
For example, "password" will always be plain password and "password64", the encoded password.
Cheers,
Vincent
The text was updated successfully, but these errors were encountered:
Currently, TM1py checks first if the "password" is encoded, then if it fails to login with the password decoded, it tries with the password as it is. It means that if you have a wrong password, TM1py is going to use 2 failed attempts instead of just 1. This can lead to reaching the maximum of attempts very quickly and locked our Admin user.
To avoid this we could add a new parameter in the config.ini, called "password64" or if we want to make it less obvious it could be "pwd", the new parameter will be used to put the encoded password. TM1py could check first if there is a value for this new parameter then it tries to connect, if there is no value, TM1py will get the password from the parameter "password".
For example, "password" will always be plain password and "password64", the encoded password.
Cheers,
Vincent
The text was updated successfully, but these errors were encountered: