HOPEX Administration (Web) : MEGA Administration-Supervisor : Managing Users : Introduction to User Management : Person Login Properties
   
Person Login Properties
To:
• create the login of a person, see "Creating Users" or "Creating the Login of a Person".
• consult login characteristics, see "Viewing Login Characteristics".
• configure the login of a person, see or "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 automatically on user creation. 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
Status (Login)
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.
*For more details, see "Products accessible on the license (Command Line)".
*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).
*See "Defining Default Authentication Mode".
Authentication mode of a user is by checking the user password. Available authentication modes are:
• MEGA
Passwords are managed and stored in the HOPEX repository.
This is default authentication mode.
*For more details, see "Authentication in HOPEX".
• 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.
*For more details, see "Windows Authentication".
• LDAP
Passwords are managed and stored in the LDAP server of the enterprise. The directory configuration is stored in options.
The HOPEX user is authenticated at the LDAP server level.
*For more details, see "LDAP Authentication".
• Custom
This authentication is managed by an external authentication module or SSO. This authentication mode is specific to Web connection to Web applications.
*See the Web connection overloading and configuration EN technical article.
Windows identifier
*This field only appears when the Authentication Mode is "Windows", see "Authentication mode".
The Windows Identifier of a user enables connection of a HOPEX user to a Windows user, see "Associating a Windows user with a HOPEX user manually".
To connect to a HOPEX application (Web Front-End), the user must enter his/her password.
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.