I am having trouble getting into the admin console

Openfire Openfire Support
1

I changed the ldap section of widlfire.xml:

But every time when I try to login to admin console it says:

Login failed: make sure your username and password are correct and that you’'re an admin or moderator.

Any ideas? I’'m sure this is an example of end user ingnorance, but I am stuck. I have adfind installed and tested the correct port and baseDN are OK (or at least the same as what adFind shows).

Thanks in advance for the help,

zepzep

Message was edited by:

zepzep

Message was edited by:

zepzep

2

If this has been answered elsewhere please point me in the right direction. I have searched these forums and the internet and news groups but no answer.

Thanks Again,

zepzep

3

zepzep,

In my config, I have a few differences. I’'ll post them and you can see if any of them work for you.

  • I have the FQDN of the host.

  • I use “sAMAccountName” for the (minus the quotes)

  • You might want to also put the whole path for the adminDN … like “CN=Administrator,DC=office,DC=test-domain,DC=com”

I’'m no LDAP guru but these work for me. Let me know if you still have issues.

PM.

4

http://www.jivesoftware.org/community/thread.jspa?threadID=17043&tstart=15

This will help. Also read the Wildfire LDAP Guide. The FAQ at the end was helpful.

5

Thanks for the reply. I made those changes:

But still no luck: same error message when trying to login to admin console. I also tried this for adminDN:

CN=jabberadmin,DC=XXX,DC=XXXX,DC=com

Which is what adfind tells me for jabberadmin.

Thanks for the reply. Any other ideas?

zepzep

Message was edited by:

zepzep

Message was edited by:

zepzep

Message was edited by:

zepzep

Message was edited by:

zepzep

6

You also have the ldap.port commented out.

7

I have the first port commented out, because I was trying global. The next line after that is

Thanks again for looking.

zepzep

Message was edited by:

zepzep

8

Also, I am getting errors like this in the wildfire server dialog:

0000: 30 4E 02 01 01 60 49 02 01 03 04 39 43 4E 3D 6A 0N…`I…9CN=j

0010: 61 62 62 65 72 61 64 6D 69 6E 2C 44 43 3D 55 73 abberadmin,DC=Us

0020: 65 72 73 2C 44 43 3D 6F 66 66 69 63 65 2C 44 43 ers,DC=XXX,DC

0030: 3D 6E 61 74 68 61 6E 2D 6E 61 74 68 61 6E 2C 44 =XXXX,D

0040: 43 3D 63 6F 6D 80 09 31 32 71 77 65 72 74 79 21 C=com…PASSWORD

9

zepzep,

For grins, can you try moving your jabberadmin ID to the DC=office? I’'m not sure if your environment will allow you to move it but I had a horrible time with my OUs that had spaces in the name. Once I moved it closer to root that had no spaces, it worked fine.

Shoot, sorry, I just saw your previous post that you tried that, sorry.

Message was edited by:

pmac2

10

Thanks for looking anyway. I appreciate it. I am about out of ideas here.

zepzep

11

Don’'t give up, I had the same problems and in my case it was something simple like the spaces in the OU name. Hang in there, someone here may shed some light on it for you.

Good luck!

12

Got it. Time to get a cold beer!

In case anyone is following this and wants the corrected config file.

Thanks to pmac2 and nish54 for the responses.

Message was edited by:

zepzep

13

Awesome!! Good for you! That beer call sure got me thirsty though !!!