The user manager defines the contributor management method.
The user manager is a single extension pointThis means that only one implementation can be used at a time. Its identifier is org.ametys.runtime.user.UsersManager.
The user manager is selected via the WEB-INF/param/runtime.xml of the application (cf. Runtime file.xml) or through thePlugins and Workspace"Available from the administration interface.
To date, the following extensions are available for this extension point:
In this implementation, the list of contributors is fixed and consists of a single "Anonymous user".
This extension must only be used in conjunction with the org.ametys.runtime.plugins.core.authentication.Defined for the CredentialsProvider.
This implementation is generally only used to demonstrate CMS Ametys .
To find out more
To define your own list of contributors, please visit the Customized static list of contributors page.
In this implementation, the user database is stored in a Jdbc database ( Users table). The database used is the application's "core" database, which can be configured in the application's configuration parameters.
User passwords are not stored in the Users table, and users cannot be modified via the CMS application.
Further information
To use your own database, please visit the Custom database contributors page.
This implementation is similar to org.ametys.runtime.plugins.core.user.CoreJdbc the user database is stored in the application's "core" database (table Users).
User passwords are not stored in the Users table, but users can be modified via the CMS application (see User administration).
Further information
To use your own database, please visit the Custom database contributors page.
In this implementation, the user base is stored in a Jdbc database ( Users table) along with their password. The database used is the application's "core" database, which can be configured in the application's configuration parameters.
Users cannot be modified via the CMS application.
This implementation is similar to org.ametys.runtime.plugins.core.user.CoreCredentialJdbc, but users can be modified via the CMS application (cf. User administration)
In this implementation, the user base is located in a LDAP
In this implementation, the user base is located in a LDAP directory and contributors can be authenticated.
This implementation combines the operation of org.ametys.runtime.plugins.core.CredentialsAwareLdap and org.ametys.runtime.plugins.core.user.CoreCredentialsAwareJdbc
CMS users can be found in either the LDAP directory or the local database.
The choice of user manager must be consistent with the choice of CredentialsProvider and AuthenticationManager. Please refer to the usage rules.