Jump to content

Recommended Posts

Posted

Found an answer on the Jivesoft website forum - you have to set the Automatic Discovery option to "off" and specify the server to use - all from the Advanced settings button on the Login box. That at least halves the startup time. Still not lightning fast though...

 

Ian

  • 3 weeks later...
Posted

@Tuxguy: Just got round to setting this up on my ICT Support server and followed tha AD config instructions from the Jivesoft site and have to say was very pleased when it worked.

 

Regarding the server you have it installed on it doesn't matter wether that is a active directory server or not you just set the ip_address to be the ip address of an AD server and then the wildfire server does an ldap lookup against it.

 

ben

Posted

I've got it set up on MS server with AD intergration, but I've never managed an RM network so I don't know what the difference might be in setup. I did post the contents of my 'wildfire.xml' further up so don't know if you can work it out from that?

 

(Thanks Tarquel for putting in Code tags. Didn't know I had to do this but I do now!!!)

Posted








true




9090
9091


administrator, SystemAdmin

en





localhost
389
sAMAccountName
displayName
mail
dc=Limehurst,dc=Internal
[email protected]
hiddenpassword
false



org.jivesoftware.wildfire.ldap.LdapUserProvider ;


org.jivesoftware.wildfire.ldap.LdapAuthProvider ;




org.jivesoftware.database.EmbeddedConnectionProvider

true

 

This xml files works on rm network but you have to create a admin2 domain admin user..

 

Not got it working with systemadmin and not got it working with staff only user yets...

 

Russell

  • 4 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...