-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/2010 01:24 PM, Stephen Gallagher wrote:
> On 01/26/2010 11:43 AM, Sumit Bose wrote:
>> I'm not sure this is a good idea, unless you want to force
>> provider=local domains to have cache_credentials=true. Right now, this
>> will break authentic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/26/2010 11:43 AM, Sumit Bose wrote:
> I'm not sure this is a good idea, unless you want to force
> provider=local domains to have cache_credentials=true. Right now, this
> will break authentication against the LOCAL domain if cache_credentials
>
On Tue, Jan 26, 2010 at 10:15:45AM -0500, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 01/21/2010 10:00 AM, Sumit Bose wrote:
> > Hi,
> >
> > although it might be good practice to check cache_credentials before
> > calling sysdb_cache_auth_send() I think it ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/21/2010 10:00 AM, Sumit Bose wrote:
> Hi,
>
> although it might be good practice to check cache_credentials before
> calling sysdb_cache_auth_send() I think it make sense to add it here,
> too. E.g. if someone forgets to check before calling
> s
Hi,
although it might be good practice to check cache_credentials before
calling sysdb_cache_auth_send() I think it make sense to add it here,
too. E.g. if someone forgets to check before calling
sysdb_cache_auth_send() and for some reason the configuration is changed
from cache_credentials=true t
