LDAP client....

[SpreadTooThin]

I am writing an application that requires a user to log in.
Rather than keeping a table of users and passwords, I'd like to use LDAP to authenticate the users. (Is that what Lightweight Director Access Protocol was intended for?)

Can someone point me to a low level document that explains the protocol?

[Rod Dorman]

Post by SpreadTooThin
I am writing an application that requires a user to log in.
Rather than keeping a table of users and passwords, I'd like to use LDAP to
authenticate the users. (Is that what Lightweight Director Access Protocol was
intended for?)
Can someone point me to a low level document that explains the protocol?

RFC 4511
Lightweight Directory Access Protocol (LDAP): The Protocol
http://www.ietf.org/rfc/rfc4511.txt

[Lew Pitcher]

On Thursday 28 November 2013 16:38, in

Post by SpreadTooThin
I am writing an application that requires a user to log in.
Rather than keeping a table of users and passwords, I'd like to use LDAP
to authenticate the users. (Is that what Lightweight Director Access
Protocol was intended for?)

Actually, no. But that shouldn't stop you from trying to use it that way.

LDAP was developed as a low-overhead alternative to the X.500 Directory
Service, which (IIRC, at the time of LDAP's development) was primarily used
as an "Address book" for electronic messaging.

Post by SpreadTooThin
Can someone point me to a low level document that explains the protocol?

As Rod said, see the RFCs

[SpreadTooThin]

Post by Lew Pitcher
On Thursday 28 November 2013 16:38, in

Post by SpreadTooThin
I am writing an application that requires a user to log in.
Rather than keeping a table of users and passwords, I'd like to use LDAP
to authenticate the users. (Is that what Lightweight Director Access
Protocol was intended for?)

Actually, no. But that shouldn't stop you from trying to use it that way.
LDAP was developed as a low-overhead alternative to the X.500 Directory
Service, which (IIRC, at the time of LDAP's development) was primarily used
as an "Address book" for electronic messaging.

Post by SpreadTooThin
Can someone point me to a low level document that explains the protocol?

As Rod said, see the RFCs
--
Lew Pitcher
"In Skills, We Trust"
PGP public key available upon request

Would i be more successful looking at auth or x-auth?

[Jorgen Grahn]

Post by SpreadTooThin

Post by Lew Pitcher
On Thursday 28 November 2013 16:38, in

Post by SpreadTooThin
I am writing an application that requires a user to log in.
Rather than keeping a table of users and passwords, I'd like to use LDAP
to authenticate the users. (Is that what Lightweight Director Access
Protocol was intended for?)

Actually, no. But that shouldn't stop you from trying to use it that way.
LDAP was developed as a low-overhead alternative to the X.500 Directory
Service, which (IIRC, at the time of LDAP's development) was primarily used
as an "Address book" for electronic messaging.

Post by SpreadTooThin
Can someone point me to a low level document that explains the protocol?

As Rod said, see the RFCs

Please fix your postings, e.g. the many extra lines.

Post by SpreadTooThin
Would i be more successful looking at auth or x-auth?

Noone told you not to use LDAP. If I understand correctly it's a
rather common way of doing it.

Perhaps you should look at what some similar software does, and how.
Some of them support a number of different methods ...

/Jorgen

[SpreadTooThin]

Post by Lew Pitcher
Actually, no. But that shouldn't stop you from trying to use it that way.