It looks like upgrading Perl is our fix. Now on to upgrading everything. :-(
It could be worse, so I will be happy that a Perl upgrade seems to have fixed
the issue.
-Jason
On Nov 8, 2013, at 9:15 AM, Heikki Vatiainen h...@open.com.au wrote:
On 11/05/2013 09:22 PM, Mueller, Jason C wrote:
Hi,
I have a problem with connecting to our Active Directory servers (LDAP)
on port 636 with radiator. Port 3269 is working but I have to use 636
for a certain reason.
The mad thing is: I cannot reproduce the problem with a little Perl
program on the same host.
System:
radiator 4.11, Debian
Addendum:
On 11/11/2013 10:58 PM, Klara Mall wrote:
I have a problem with connecting to our Active Directory servers (LDAP)
on port 636 with radiator. Port 3269 is working but I have to use 636
for a certain reason.
The mad thing is: I cannot reproduce the problem with a little Perl
On 10/30/2013, Heikki Vatiainen wrote:
Great, I'll get back to you when we have something to test.
Hello David,
EAP_25.pm in the current patches now sets $context-{inner_identity} as
soon as the inner EAP figures it out.
If you have time to test this, please let us know how it goes.
On 11/09/2013 01:22 AM, David Zych wrote:
Now, however, I'm trying to put my Radiator servers behind a server load
balancer (SLB); every few seconds, the SLB sends a health check request which
Radiator is configured to REJECT (this is safer than ACCEPT and equally
effective proof that the
On 11/11/2013 11:58 PM, Klara Mall wrote:
With this configuration the connection fails about half of the time (not
always) with:
ERR: Could not open LDAP connection to ad.example.com:636. Backing off
for 600 seconds.
I had a look at Ldap.pm from the radiator code and wrote this little
