The visitor manager defines the visitor management method. It is necessary to define a visitor base if the site has pages with limited access.
This is a single extension pointThis means that only one implementation can be used at a time. Its identifier is org.ametys.runtime.user.UsersManager.FO.
The visitor manager is selected via the WEB-INF/param/runtime.xml site 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:
 |
Important
Choosing the extension point org.ametys.runtime.user.UsersManager.FO must correlate with the choice made by the site application's user manager.
Please refer to the correspondence table for visitor managers.
org.ametys.web.frontoffice.DefaultFrontOfficeUsersManager
This implementation is used when site visitors are in the same database as CMS contributors.
This can be used, for example, for an Intranet or a wiki...
org.ametys.web.frontoffice.user.Jdbc
In this implementation, the user base is stockée in a Jdbc database (table FOUsers).
User passwords are not stored in this database, and users cannot be modified via the application: it is therefore necessary to point to a database already managed with another tool, and to be authenticated via SSO.
org.ametys.web.frontoffice.user.ModifiableJdbc
This implementation is similar to org.ametys.web.frontoffice.user.Jdbc.
User passwords are not stored in the FOUsers table, but users can be modified via the CMS application.
org.ametys.web.frontoffice.user.CredentialsAwareJdbc
In this implementation, the user base is stored in a Jdbc database (table FOUsers) along with their password.
The list of visitors cannot be modified via the CMS application.
org.ametys.web.frontoffice.user.ModifiableCredentialsAwareJdbc
In this implementation, the user base is stored in a Jdbc database (table FOUsers) along with their password.
The list of visitors can be modified via the CMS application.
org.ametys.web.frontoffice.user.SiteAwareJdbc
This implementation is similar to org.ametys.web.frontoffice.user.Jdbc but each site has its own its own list of visitors
org.ametys.web.frontoffice.user.ModifiableSiteAwareJdbc
This implementation is similar to org.ametys.web.frontoffice.user.ModifiableJdbc but each site has its own list of visitors
org.ametys.web.frontoffice.user.CredentialsAwareSiteAwareJdbc
This implementation is similar to org.ametys.web.frontoffice.user.CredentialsAwareJdbc but each site has its own list of visitors
org.ametys.web.frontoffice.user.ModifiableCredentialsAwareSiteAwareJdbc
This implementation is similar to org.ametys.web.frontoffice.user.ModifiableCredentialsAwareJdbc but each site has its own list of visitors
org.ametys.web.frontoffice.LdapAndSqlFrontOfficeUsersManager
In this implementation, visitors to the site can be found either in a directory LDAP, or in a database.
org.ametys.web.frontoffice.LdapAndSqlFrontOfficeSiteAwareUsersManager
This implementation is similar to org.ametys.web.frontoffice.LdapAndSqlFrontOfficeUsersManager but each site has its own list of visitors
Back to top