Logon: Difference between revisions
Created page with "Check Default Username & Password for credentials. Note that your username and password is stored in a database table. This means that if you create more than one database (host) then your username and password will be specific to the database that your connecting to. The first time you logon you will be prompted to change the password. There are a number of settings in the System Keys screen which control the complexity of the password and the frequency of ch..." |
Updated by push_wiki.py |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
The Logon screen is presented when Commander4j starts in Desktop mode. It requires a valid username and password before access to any part of the application is granted. | |||
== Credentials == | |||
Usernames and passwords are stored in the Commander4j database (table `SYS_USERS`), not in the operating system. Each database instance has its own independent set of user accounts. If you connect to a different database host, you will need credentials valid for that database. | |||
For the default credentials on a fresh installation, see [[Default Username & Password]]. | |||
== Login Process == | |||
The system performs the following checks in order when a login is attempted: | |||
# '''Account exists''' — the username must exist in the database. | |||
# '''Account enabled''' — accounts can be disabled by an administrator. A disabled account cannot log in. | |||
# '''Account locked''' — accounts are locked automatically after exceeding the maximum number of failed password attempts (configurable via [[System Keys]]). Locked accounts can be set to unlock automatically after a specified number of minutes, or may require an administrator to unlock them manually via the [[Users]] screen. | |||
# '''Account expiry''' — if the account has an expiry date set and that date has passed, login is refused. | |||
# '''Password correct''' — the entered password is validated. Each failed attempt increments the bad attempt counter. | |||
# '''Password expiry''' — if the password expiry feature is enabled and the password has not been changed within the configured number of days, the user is prompted to change it. | |||
# '''Password change required''' — if an administrator has set this flag, the user must choose a new password before proceeding. | |||
== First Login == | |||
On a fresh installation, the system will prompt you to change the default password immediately after your first successful login. | |||
== Windows Authentication == | |||
Commander4j pre-populates the username field with the currently logged-in Windows username. If your Commander4j user ID matches your Windows username, you may only need to enter your password. | |||
== Changing Your Password == | |||
The logon screen includes a '''Change Password''' option. Ticking this before logging in will prompt for a password change immediately after a successful login, even if the system has not required it. | |||
Passwords can also be changed at any time through the web scanner interface ([[Web_Applications_Overview|c4j_web_react]]) if you are a shop-floor user without desktop access. | |||
== Account Recovery == | |||
If your account is locked, contact your Commander4j administrator. They can unlock the account via the [[Users]] screen. If auto-unlock is configured, the account will unlock automatically after the configured number of minutes without administrator intervention. | |||
See also: [[Users]], [[Default Username & Password]], [[System Keys]], [[Groups]], [[Permissions]] | |||
[[Category:Commander4j]] | |||
Latest revision as of 12:09, 1 April 2026
The Logon screen is presented when Commander4j starts in Desktop mode. It requires a valid username and password before access to any part of the application is granted.
Credentials
Usernames and passwords are stored in the Commander4j database (table `SYS_USERS`), not in the operating system. Each database instance has its own independent set of user accounts. If you connect to a different database host, you will need credentials valid for that database.
For the default credentials on a fresh installation, see Default Username & Password.
Login Process
The system performs the following checks in order when a login is attempted:
- Account exists — the username must exist in the database.
- Account enabled — accounts can be disabled by an administrator. A disabled account cannot log in.
- Account locked — accounts are locked automatically after exceeding the maximum number of failed password attempts (configurable via System Keys). Locked accounts can be set to unlock automatically after a specified number of minutes, or may require an administrator to unlock them manually via the Users screen.
- Account expiry — if the account has an expiry date set and that date has passed, login is refused.
- Password correct — the entered password is validated. Each failed attempt increments the bad attempt counter.
- Password expiry — if the password expiry feature is enabled and the password has not been changed within the configured number of days, the user is prompted to change it.
- Password change required — if an administrator has set this flag, the user must choose a new password before proceeding.
First Login
On a fresh installation, the system will prompt you to change the default password immediately after your first successful login.
Windows Authentication
Commander4j pre-populates the username field with the currently logged-in Windows username. If your Commander4j user ID matches your Windows username, you may only need to enter your password.
Changing Your Password
The logon screen includes a Change Password option. Ticking this before logging in will prompt for a password change immediately after a successful login, even if the system has not required it.
Passwords can also be changed at any time through the web scanner interface (c4j_web_react) if you are a shop-floor user without desktop access.
Account Recovery
If your account is locked, contact your Commander4j administrator. They can unlock the account via the Users screen. If auto-unlock is configured, the account will unlock automatically after the configured number of minutes without administrator intervention.
See also: Users, Default Username & Password, System Keys, Groups, Permissions