Hybrid authentication methods, pls help

Openfire Openfire Support
#1

We have two sets of users, one is on an LDAP server, the other is local unix accounts. We are trying to configure Wildfire to allow both sets of users to login. Right now, I’'m able to make either work individually, but not together. Can anyone tell me if this is doable with the current state of the wildfire? and if so, shed some light pls.

Thanks a lot,

Hao

#2

Good news, it is possible!

This is directly from the JavaDoc of the HybridAuthProvider.

The hybrid auth provider allows up to three AuthProvider implementations to

be strung together to do chained authentication checking. The algorithm is

as follows:

  1. Attempt authentication using the primary provider. If that fails:

  2. If the secondary provider is defined, attempt authentication (otherwise return).

If that fails:

  1. If the tertiary provider is defined, attempt authentication.

To enable this provider, set the following in the XML configuration file:

Each of the chained providers can have a list of override users. If a user is in

an override list, authentication will only be attempted with the associated provider

(bypassing the chaining logic).

The full list of properties:

  • hybridAuthProvider.primaryProvider.className (required) – the class name

of the auth provider.

  • hybridAuthProvider.primaryProvider.overrideList – a comma-delimitted list

of usernames for which authentication will only be tried with this provider.

  • hybridAuthProvider.secondaryProvider.className – the class name

of the auth provider.

  • hybridAuthProvider.secondaryProvider.overrideList – a comma-delimitted list

of usernames for which authentication will only be tried with this provider.

  • hybridAuthProvider.tertiaryProvider.className – the class name

of the auth provider.

  • hybridAuthProvider.tertiaryProvider.overrideList – a comma-delimitted list

of usernames for which authentication will only be tried with this provider.

73 *

The primary provider is required, but all other properties are optional. Each provider

should be configured as it is normally, using whatever XML configuration options it specifies.

#3

It works! Thanks a lot!

Here is my configuration for people who have similar interests.







]]>

cn

mail

cn

member

description

false

(objectClass=group)

org.jivesoftware.wildfire.auth.NativeAuthProvider

org.jivesoftware.wildfire.user.NativeUserProvider

shaj