* LDAP binding
@ 2004-10-13 11:12 linux user
2004-10-13 15:08 ` raven
2004-10-13 19:03 ` Timo Felbinger
0 siblings, 2 replies; 3+ messages in thread
From: linux user @ 2004-10-13 11:12 UTC (permalink / raw)
To: autofs
Dear all,
We have Redhat Linux clients that are migrating from NIS to LDAP
using the RFC2307, the ldap server is a SUN ONE DS 5.1 which runing on
a Solaris 8.0, The linux clients (different red hat releases 7.3,8.0,
RHEL 2.1, and 3.0)
We could not do autofs lookups as they seem to be binding anonoumsly
as seen from the log files, also from the code we can see that is the
case as follows :
file modules/lookup_ldap.c:
ldap_simple_bind_s(ldap, NULL, NULL); /* LDAPv3 */
But in fact, according to the OpenLDAP header file (ldap.h):
ldap_simple_bind_s(LDAP *ld, char *who, char *passwd);
So, my question is would that be changed to bind using simple bind by
passing the credniatls as seen in the configration files later on? the
who, and the password in the above lookup_ldap.c function, as we do
not have control over the ldap server as its run by different
department, and they require us to do a simple bind passing
credentials.
also what is the status of autofs when it comes to using LDAPS instead
over SSL/TLS instead of just standard ldap.
TIA
regards
W. Shaari
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: LDAP binding
2004-10-13 11:12 LDAP binding linux user
@ 2004-10-13 15:08 ` raven
2004-10-13 19:03 ` Timo Felbinger
1 sibling, 0 replies; 3+ messages in thread
From: raven @ 2004-10-13 15:08 UTC (permalink / raw)
To: linux user; +Cc: autofs
On Wed, 13 Oct 2004, linux user wrote:
> Dear all,
>
> We have Redhat Linux clients that are migrating from NIS to LDAP
> using the RFC2307, the ldap server is a SUN ONE DS 5.1 which runing on
> a Solaris 8.0, The linux clients (different red hat releases 7.3,8.0,
> RHEL 2.1, and 3.0)
>
> We could not do autofs lookups as they seem to be binding anonoumsly
> as seen from the log files, also from the code we can see that is the
> case as follows :
>
> file modules/lookup_ldap.c:
> ldap_simple_bind_s(ldap, NULL, NULL); /* LDAPv3 */
>
> But in fact, according to the OpenLDAP header file (ldap.h):
> ldap_simple_bind_s(LDAP *ld, char *who, char *passwd);
>
> So, my question is would that be changed to bind using simple bind by
> passing the credniatls as seen in the configration files later on? the
> who, and the password in the above lookup_ldap.c function, as we do
> not have control over the ldap server as its run by different
> department, and they require us to do a simple bind passing
> credentials.
Possible. I don't have any sample code for grabing stuff from the config
file. I hope this would be available within the LDAP api as we don't have
any way of knowing where the config may be located.
>
> also what is the status of autofs when it comes to using LDAPS instead
> over SSL/TLS instead of just standard ldap.
Drom what I've seen adding TLS support to the code is reasonably straight
forward but again finding out if it's required and how, in a system
independant manner is a problem. Additionally, there can be other
related requirements for the exchange when using TLS.
Basically, I haven't looked into this at all yet.
Ian
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: LDAP binding
2004-10-13 11:12 LDAP binding linux user
2004-10-13 15:08 ` raven
@ 2004-10-13 19:03 ` Timo Felbinger
1 sibling, 0 replies; 3+ messages in thread
From: Timo Felbinger @ 2004-10-13 19:03 UTC (permalink / raw)
To: autofs
On Wed, 13 Oct 2004, linux user wrote:
> Dear all,
>
> We have Redhat Linux clients that are migrating from NIS to LDAP
> using the RFC2307, the ldap server is a SUN ONE DS 5.1 which runing on
> a Solaris 8.0, The linux clients (different red hat releases 7.3,8.0,
> RHEL 2.1, and 3.0)
>
> We could not do autofs lookups as they seem to be binding anonoumsly
> as seen from the log files, also from the code we can see that is the
> case as follows :
>
> file modules/lookup_ldap.c:
> ldap_simple_bind_s(ldap, NULL, NULL); /* LDAPv3 */
>
> But in fact, according to the OpenLDAP header file (ldap.h):
> ldap_simple_bind_s(LDAP *ld, char *who, char *passwd);
>
> So, my question is would that be changed to bind using simple bind by
> passing the credniatls as seen in the configration files later on? the
> who, and the password in the above lookup_ldap.c function, as we do
> not have control over the ldap server as its run by different
> department, and they require us to do a simple bind passing
> credentials.
I don't know about simple bind with credentials; I've never tried that.
However if "SASL external" (ie, basically RSA public key authentication
via client certificates) would work for you as a client authentication
mechanism, I can confirm that it is possible to get this to work with
autofs. Since you are asking for TLS, your server is probably already
using server certificates to authenticate itself to the clients. I'm
currently configuring our clients to do essentially the reverse and use
the ssh_host_rsa_key (which every client has anyway) to authenticate
itself to the server.
I can post a patch if someone is interested, but I need to put some
more work into it to make it a little less ugly...
> also what is the status of autofs when it comes to using LDAPS instead
> over SSL/TLS instead of just standard ldap.
This part is already working fine and stable here.
I posted a link to a modified lookup_ldap module which can speak TLS a
little while ago (http://www.timof.qipc.org/autofs-4.1.3-patch).
Regards,
Timo Felbinger
--
Timo Felbinger <Timo.Felbinger@physik.uni-potsdam.de>
Quantum Physics Group http://www.quantum.physik.uni-potsdam.de
Institut fuer Physik Tel: +49 331 977 1793 Fax: -1767
Universitaet Potsdam, Germany
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-10-13 19:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-10-13 11:12 LDAP binding linux user
2004-10-13 15:08 ` raven
2004-10-13 19:03 ` Timo Felbinger
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.