On Tue, Jul 24, 2012 at 6:09 PM, Oliver Loch wrote:
> you have to map the local UID to the corresponding ldap-user.
>
>
ldapi was working right (I've done a similar job using heimdal instead of
MIT).
But looks like ldapi is just ignored by kdb5_ldap_util. Does anyone else
have some idea or shoul
On 07/25/2012 05:26 AM, Javier Palacios wrote:
> But looks like ldapi is just ignored by kdb5_ldap_util. Does anyone else
> have some idea or should I file a bug report?
We don't have support for SASL authentication in our LDAP back end, so
the KDC can't use SASL EXTERNAL to autobind over ldap. S
Hi, I have a question. Does KDC cache anything from ldap?
That is, if I update ldap, KDC will see the results immediately?
Thanks
Jim
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
On Wed, 2012-07-25 at 10:51 -0700, Jim Shi wrote:
> Hi, I have a question. Does KDC cache anything from ldap?
No.
> That is, if I update ldap, KDC will see the results immediately?
Yes.
Simo.
--
Simo Sorce * Red Hat, Inc * New York
Kerberos ma
On Wed, Jul 25, 2012 at 6:13 PM, Greg Hudson wrote:
> On 07/25/2012 05:26 AM, Javier Palacios wrote:
> > But looks like ldapi is just ignored by kdb5_ldap_util. Does anyone else
> > have some idea or should I file a bug report?
>
> We don't have support for SASL authentication in our LDAP back en
On Wed, 2012-07-25 at 20:20 +0200, Javier Palacios wrote:
> On Wed, Jul 25, 2012 at 6:13 PM, Greg Hudson wrote:
>
> > On 07/25/2012 05:26 AM, Javier Palacios wrote:
> > > But looks like ldapi is just ignored by kdb5_ldap_util. Does anyone else
> > > have some idea or should I file a bug report?
>
On 07/25/2012 02:20 PM, Javier Palacios wrote:
> OK. But as far as I understand, SASL EXTERNAL is somewhat equivalent to
> ldapi, and documentation states that ldapi is a valid protocol to
> communicate with ldap, which does not look the case.
That does not precisely match my understanding.
ldapi
