Howto Setup the Hybrid Authentication Provider to use LDAP and Database

Openfire may use more than one authentication provider at a time. One may use LDAP as the primary provider and the Database as a secondary.

To chain-in the hybrid{Auth,User}Provider-class, one have to

• link its 1st destination to the LdapAuthProvider-class
• link its 2nd destination to the Default{Auth,User}Provider-class (that will use the database)
• use it as the new value for the provider.{auth,user}-class

This might be done by adding/changing the following System Properties at the Server Manager GUI page. Consider to make a database backup before applying the changes; you may kick yourself by entering wrong things because whole authorisation may become inoperable.

Tag	Value	Default
hybridAuthProvider.primaryProvider.className	org.jivesoftware.openfire.ldap.LdapAuthProvider	org.jivesoftware.openfire.auth.DefaultAuthProvider
hybridUserProvider.primaryProvider.className	org.jivesoftware.openfire.ldap.LdapUserProvider
hybridAuthProvider.secondaryProvider.className	org.jivesoftware.openfire.auth.DefaultAuthProvider
hybridUserProvider.secondaryProvider.className	org.jivesoftware.openfire.user.DefaultUserProvider
provider.auth.className	org.jivesoftware.openfire.auth.HybridAuthProvider	org.jivesoftware.openfire.auth.DefaultAuthProvider
provider.user.className	org.jivesoftware.openfire.user.HybridUserProvider	org.jivesoftware.openfire.user.DefaultUserProvider