Jason Alderfer wrote:
the function ldap_postauth in rlm_ldap.c still looks for Ldap-UserDn
in request-packet-vps.
The attached patch updates ldap_postauth to check the control items, which
solves the problem for me. I assume that's the best way to fix it.
I've added the patch, thanks.
Hi Jason,
with the answer from Alan we have found the dn-information in the control
item. You must use %{control:Ldap-UserDn} instead of %{Ldap-UserDn}
Regards,
Christan
On Monday 14 April 2008 23:18:42 Jason Alderfer wrote:
Jason Alderfer wrote:
I'm testing upgrading to 2.0.3 from 1.1.7
Hi Jason,
with the answer from Alan we have found the dn-information in the control
item. You must use %{control:Ldap-UserDn} instead of %{Ldap-UserDn}
Perfect. Unlang works now. Thanks.
However, there is still the problem with postauth.
the function ldap_postauth in rlm_ldap.c still
Hello,
I'm testing upgrading to 2.0.3 from 1.1.7 and it appears that the LDAP
module in 2.0.3 is not setting the Ldap-UserDn in a way that is available
for further analysis. The problem shows up when using
edir_account_policy_check = yes and PEAP. This is the error from the
debug output.
+-
Jason Alderfer wrote:
Hello,
I'm testing upgrading to 2.0.3 from 1.1.7 and it appears that the LDAP
module in 2.0.3 is not setting the Ldap-UserDn in a way that is available
for further analysis.
It's now in the control item list. This should be better documented...
If I change it to
Jason Alderfer wrote:
I'm testing upgrading to 2.0.3 from 1.1.7 and it appears that the LDAP
module in 2.0.3 is not setting the Ldap-UserDn in a way that is
available
for further analysis.
It's now in the control item list. This should be better
documented...
But the function
6 matches
Mail list logo