Overview

You can override the standard Traverse authentication methods by creating your own plugin Java classes or scripts. This allows the use of custom authentication databases or other site-specific authentication methods to control access to Traverse. Note that although it is possible to use an external authentication source, the authorization information (permissions, limits, etc.) are still stored in the Traverse provisioning database. So it will be necessary to create the login ID on the Traverse database even though that login is authenticated from an external database.

Additionally, Traverse provides the facility for integrating with a web portal and using the web portal's authentication mechanism.

Note: If you change the authentication mechanism, the changes are applied only to users created after the change was made.

To use the new authentication method for users created before the authentication mechanism changed, you must change their passwords using either the web application or the BVE TCP server (see userClass.update. Otherwise, older users will continue to be authenticated by the old mechanism (e.g., the Traverse internal password database).

Note: Changes to emerald.xml need to be reinstated on an upgrade since all changes might not be copied over during an upgrade.