HOPEX Administration > Administrator Guide > Managing Users > Introduction to User Management > Login Properties
Login Properties
To:
• view login characteristics, see Viewing the Login Characteristics.
• configure a login, see Defining the Login of a Person.
User code  
The User Code is the short identifier (upper case, maximum length 6 characters) of the user that serves as the basis for private workspace naming.
This code is defined at creation of the user. To ensure data consistency, it should not be modified.
Example: PDD
Login Holder 
The login holder is the person associated with the login.
Example: DURAND Pierre
Inactive user (Status) 
Login status can be used to make a user inactive (value: Inactive). The user no longer has access to repositories, but trace of his/her actions is retained. The user can be easily reactivated (value: Active).
*When you delete a user from the repository, the commands connected to this user become orphans and you lose part of the history saved in logs. With Inactive status, the user no longer has access to repositories, but the history of commands connected to the user is kept in logs.
Products accessible on the license (Command Line) 
The Command Line field enables restriction of access of a user or profile to available products.
*If a user is connected to a profile and the user and profile each have access to products restricted by the Command Line attribute, the products accessible to the user are at the intersection of the values of the Command Line attribute of the user and profile.
Authentication mode 
Default value of the Authentication Mode parameter on the user login is inherited at user creation from the Authentication Mode option defined in the options of the environment (Options > Installation > User Management).
Authentication mode of a user is by checking the user password. Available authentication modes are:
• MEGA
The HOPEX authentication service checks that the password entered matches the password stored (hashed and encrypted) in HOPEX repository.
This is default authentication mode.
• LDAP
Passwords are managed and stored in the LDAP server of the enterprise. The directory configuration is stored in HOPEX options.
The HOPEX user is authenticated at the LDAP server level.
*For more details, see Configuring LDAP authentication.
• Windows
Passwords are managed and stored in Windows. This allows the user connected to Windows to be recognized automatically when he/she is connected to HOPEX (Windows Front-End), not requiring entry of his/her password.
*Attention: to connect to a HOPEX (Web Front-End) application, the user must enter his/her password.
The list of users in your HOPEX environment is automatically synchronized with the list of users defined in your Windows network.
This authentication mode corresponds to unique authentication (SSO).
*For more details, see Configuring Windows Authentication.
LDAP server 
*This field only appears when the Authentication Mode is "LDAP", see Authentication mode.
The LDAP Server is the server with which the HOPEX user is authenticated in LDAP authentication mode.
This server contains the LDAP directory in which the HOPEX user is registered.