Wildfire & Active Directory

Openfire Openfire Support
1

Hey all, been trying to get Wildfire to Authenticate with my Active Directory here, and havent had any luck.

Ive Perused the forums, and looked at many of the other posts about such, but again, no luck.

I had no problems getting wildfire set up by default, able to log in, and create accounts. However once I did the modifications to the wildfire.xml so that it should authenticate with Active Directory, I am unable to log into the Admin Console.

I am guessing I am missing something small, but I just cant see it. Any help is appreciated, as I dont know where to look from here.

Thanks in advance.

/b

2

The authorized username value should match a username in the directory (specifically, the sAMAccountName attribute). That would be in the form testc instead of testc@sf.internal. In case it helps, here’'s a snippet from my test AD setup that works:

<admin>     <authorizedUsernames>matt, admin</authorizedUsernames>  </admin>
  <ldap>     <host>activedirectory</host>      <port>389</port>      <usernameField>sAMAccountName</usernameField>      <nameField>displayName</nameField>      <emailField>mail</emailField>      <baseDN>cn=Users,dc=activedirectory,dc=pdx-int,dc=jivesoftware,dc=com</baseDN>      <adminDN>cn=Administrator,cn=Users,dc=activedirectory,dc=pdx-int,dc=jivesoftware,dc=com</adminDN>      <adminPassword>Change123</adminPassword>    </ldap>    <provider>     <user>       <className>org.jivesoftware.wildfire.ldap.LdapUserProvider</className>     </user>      <auth>       <className>org.jivesoftware.wildfire.ldap.LdapAuthProvider</className>     </auth>
    <group>
      <className>org.jivesoftware.wildfire.ldap.LdapGroupProvider</className>     </group> </provider>

Regards,

Matt

3

I’'ve tried both just the name and name@xx.xxx in the authorizedUsernames

and I have the same issue.

I sent through and grabbed your example, and subbed the info from my setup here

and I still cant log into admin console.

I know once I figure out what it is I am going to kick myself.

4

Unfortunately, it can be really through these issues using just the XML config file. The GUI setup in 3.1 will be much better. Have you tried the debug setting yet? It will print out all traffic to the LDAP server and might help you figure out what’'s going on.

-Matt

5

I’'ll give the debugger a try, and see what I can find.

Whats the ETA on 3.1, maby itl just behoove me to wait for that.

6

3.1 should be out at the very end of the month.

Regards,

Matt

7

Here is my LDAP section that is working fine for our WF testing system.

Jason