On Wed, Jun 26, 2013 at 01:55:28PM +0200, Jakub Hrozek wrote:
> On Wed, Jun 26, 2013 at 01:15:00PM +0200, Sumit Bose wrote:
> > Hi,
> >
> > with this patch the PAC responder is not started automatically if the AD
> > provider is configured, because there are configurations, e.g.
> > ldap_id_mappin
On Wed, Jun 26, 2013 at 08:57:24AM -0400, Simo Sorce wrote:
> On Wed, 2013-06-26 at 13:55 +0200, Jakub Hrozek wrote:
> > On Wed, Jun 26, 2013 at 01:15:00PM +0200, Sumit Bose wrote:
> > > Hi,
> > >
> > > with this patch the PAC responder is not started automatically if the AD
> > > provider is conf
On Wed, 2013-06-26 at 13:55 +0200, Jakub Hrozek wrote:
> On Wed, Jun 26, 2013 at 01:15:00PM +0200, Sumit Bose wrote:
> > Hi,
> >
> > with this patch the PAC responder is not started automatically if the AD
> > provider is configured, because there are configurations, e.g.
> > ldap_id_mapping = Fal
On Wed, Jun 26, 2013 at 01:15:00PM +0200, Sumit Bose wrote:
> Hi,
>
> with this patch the PAC responder is not started automatically if the AD
> provider is configured, because there are configurations, e.g.
> ldap_id_mapping = False, which are not handled properly by the PAC
> responder. When thi
Hi,
with this patch the PAC responder is not started automatically if the AD
provider is configured, because there are configurations, e.g.
ldap_id_mapping = False, which are not handled properly by the PAC
responder. When this is fixed it might be enabled again.
bye,
Sumit
From ef7814c7ad1ea5624
