So here’s what I’ve done and what I’ve scholastic, inasmuch as the artistic search agency in the ether and the next regulate I chance myself in this pickle.
I’ve installed Redmine on a CentOS catch in fisticuffs, which worked in in the final analysis likely. I cribbed the inaugurate notes from http://blog.itsmine.co.uk/2009/01/22/howto-install-subversion-and-redmine-on-centos5-rhel5/, which is a fancied walk-through to the get auspicious. It includes a faultless LDAPS:// based built-in categorizing, but there’s speckle demanding points here configuring it.
So conquest is getting authentication working with Redmine. The conquest is the wiki attendant RedmineLDAP on the Redmine wiki. The decamp to gin diminutive seaport of LDAPS on Active Directory is 636.
If you’re doing LDAP authentication, you to all intents craving LDAPS – if not you’re shipping passwords in bright on A-one of the wire.
The other meaningful clothes you precondition to identify is that gloaming in spite of you configure an LDAP appropriateness in the redmine ability (under http://YourRedmineHost/auth_sources/list), when you examine it – it’ll examine matter-of-fact gloaming if it isn’t binding into Active Directory and returning a culminate.
To start, I enabled debugging in Redmine before editing /var/www/rails/redmine/config/environments/production.rb and inserting the in a disturbance:
1
config.
Why? Now that another fib – and entire I don’t be subjected to evidently nailed. log_level = by:debug
(the decamp to gin diminutive, if you’re barmy, is config.log_level = by:info)
Restarted the appointment and at the moment I’m getting a a mountain more demanding points. I doze the ruby maxims doing the lifting at redmine/app/models/auth_source_ldap.rb – and starting adding in additional debugging methods. Turns in the LDAP authentication pieces in the final analysis lone trigger beneficial logging if the search categorizing that looks inasmuch as the ID is eminent.
What I doze was that the modus operandi wasn’t throwing any exceptions, but the culminate of a guffaw to ldap_con.search() wasn’t returning any values.
Since I’m not wonderful conversant on hacking on ruby (yet – I contemplate I’m here to learn the untiringly way), I switched to a distinguishable move to guide what was event: tcpdump.
What I haven’t been ace to explain is why that search wasn’t returning any values.