...
Solution: The feature that determines this time frame is configurable in the global settings of a particular XTM Cloud instance (administrative privileges required!), in Configuration → Settings → Security → Authentication → Disable account after non-use (days).
...
| Note |
|---|
IMPORTANT! The account disablement feature is designed to function based on the number of full days elapsed since the last account activity + 24H. In the example above, if you have the said option set to 1 day, your account will be blocked after two full days of inactivity! This stems from the difference between the time hard coded on servers, and your local time. |
Therefore, there is no other option for you to log in than just to contact your project manager or administrator to unblock your account directly in the XTM Cloud UI.
...
Allowed log on attempts → It specifies how many times users can make failed login attempts. If set to 0, no such restriction is in effect;Disable account after non-use (days) → It specifies how long (in days) your account can remain active after the last login;
| Note |
|---|
IMPORTANT! The password duration feature is designed to function based on the number of full days elapsed since the last password change + 24H. In this context, if you have a password duration set to 1 day and change your password at 3:00 PM, the system will still consider your password valid until 3:00 PM of the next day. This is because less than 48 hours (2 full days) have passed. Therefore, your password will be valid for almost two full days before the system prompts you to change it. This stems from the difference between the time hard coded on servers, and your local time. |
Computer activation level → It specifies which users are subject to the computer activation protocol. If enabled, each user attempting to log in from another browser, cleared browser or another computer will receive an activation email to activate a new browser or a device.
...