It´s work.
I write into the ldap.attrmap:
checkItem Cleartext-Password userPassword
In the sites-available/default, I comment out everything except ldap, eap
And I activate LDAP in the sites-available/inner-tunnel authorize.
Thank you for help.
-
List info/subscribe/unsubscribe? See
Here are a couple of things to check which often trip folks up:
1) is the userPassword attribute defined in $RADDB/ldap.attrmap ?
By default it isn't (I've never understood why it isn't) You should have
a line in that file which looks like this:
checkItem Cleartext-Password
Lionne Stangier wrote:
I used ldapsearch -h ldap -b dc=allesklar,dc=com -x uid=lionne.stangier
I get the userPassword but encoded :(
as... what?
Is it a secret?
Do you want people to help you?
Alan DeKok.
-
List info/subscribe/unsubscribe? See
as... what?
Is it a secret?
Sorry I don't know as what. On the LDAP Server it's clear text. Before it was
md5, maybe it's still md5. I can´t change any settings on the LDAP Server a
other admin in our company changed something for me.
I will set up a own test LDAP now.
-
List
Lionne Stangier wrote:
as... what?
Is it a secret?
Sorry I don't know as what.
Maybe someone on this list can help you, if you're willing to share
more information?
Or... you can keep posting it doesn't work.
On the LDAP Server it's clear text. Before it was md5, maybe it's
still
On 07/19/2010 08:17 AM, Lionne Stangier wrote:
Here are a couple of things to check which often trip folks up:
1) is the userPassword attribute defined in $RADDB/ldap.attrmap ?
By default it isn't (I've never understood why it isn't) You should have
a line in that file which looks like this:
Is there a double colon (::) after the userPassword attribute name in
the ldapsearch result? (e.g. userPassword:: x). If so
that means the attribute value was binary (had some non-ascii printing
character in it) so it was base64 encoded. This is a bit obscure, I
got
On 07/19/2010 10:13 AM, Lionne Stangier wrote:
Is there a double colon (::) after the userPassword attribute name in
the ldapsearch result? (e.g. userPassword:: x). If so
that means the attribute value was binary (had some non-ascii printing
character in it) so it was base64
Lionne Stangier wrote:
Yes the password it´s like you describe. I tested different forms in the
ldap.attrmap now. Same trouble as before.
Then the problem is the same as before.
1) make sure that FreeRADIUS can read the passwords from LDAP. Right
now, it can't.
2) make sure that the
On 07/19/2010 10:20 AM, Lionne Stangier wrote in a private email:
Thank you.
I have to talk with the LDAP Admin. He should save the password clear text now.
[ Replying to the list even though this was a private email because I
think this is important information ]
I just also want to make
10 matches
Mail list logo
