On 05/15/2013 06:19 AM, Jeff Blaine wrote: > Well, here's where I asked the community to share what works: > > http://lists.bestpractical.com/pipermail/rt-users/2012-February/075085.html > > And here's 1 (of 2) contributions I got and submitted, still sitting > in a github pull request that has not been merged after 1+ years: > > https://github.com/bestpractical/rt-authen-externalauth/pull/2 > > That was the "water testing" and end of my contributions to RT, > as a failed experiment. I didn't bother submitting the 2nd > config contribution I got based on the above.
I just responded to your PR. Thanks for pointing it out again. We manage a lot of repos and only use github for publishing public mirrors and receiving PRs. Sometimes this means PRs slip through the cracks if no one prods us. That is to say: if anyone thinks they're owed a response on a PR or patch or any other contribution, please do pipe up to get our attention again. I'm sorry your contributing experience was lousy. > Here's someone else's code contribution from 1+ years ago to > allow secure LDAP: > > https://github.com/bestpractical/rt-authen-externalauth/pull/1 That is an unnecessary change, and should have been closed long ago. I've now done so. The simple solution is specifying a server of "ldaps://example.com" instead of just "example.com". -- RT Training in Seattle, June 19-20: http://bestpractical.com/training
