Properties of a Person Group Login
The login of a person group is created automatically on creation of the person group.
To:
• create a person group, see Creating a Person Group.
• view login characteristics, see Viewing the Login Characteristics.
• define the login of a person group, see Modifying a Person Group Login.
User code
The User Code is the short identifier (upper case, maximum length 6 characters) of the person group.
This code is defined automatically on creation of the person group.
E.g.: SUPPOR
Login Holder
The login holder is the person group associated with the login.
E.g.: Support France
Inactive person group (Status)
Login status can be used to make a person group inactive (value: Inactive). Users belonging to the person group can no longer have access to repositories through the person group, but trace of their actions are retained. The person group can be easily reactivated (value: Active).
When you delete a person group from the repository, the commands connected to the users belonging to the person group are kept as long as the users are not deleted. Command line
The Command line field is of no use for a person group.
Authentication mode (case of authentication managed within HOPEX)
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
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 Configuring LDAP 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 Configuring LDAP Authentication.LDAP server
This field only appears when the Authentication Mode is "LDAP", see Authentication mode (case of authentication managed within HOPEX).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.