[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: kpasswd

To: Allan Streib <astreib@indiana.edu>
Subject: Re: kpasswd
From: Igor Brezac <igor@ipass.net>
Date: Fri, 17 Oct 2003 17:49:13 -0400 (EDT)
Cc: Paul M Fleming <pfleming@siumed.edu>, Howard Chu <hyc@highlandsun.com>, "'Frank Swasey'" <Frank.Swasey@uvm.edu>, "'Allan E Johannesen'" <aej@WPI.EDU>, openldap-software@OpenLDAP.org
In-reply-to: <860BF35E-00E9-11D8-8CF1-000393033826@indiana.edu>
References: <860BF35E-00E9-11D8-8CF1-000393033826@indiana.edu>

On Fri, 17 Oct 2003, Allan Streib wrote:

> On Friday, October 17, 2003, at 03:54 PM, Paul M Fleming wrote:
>
> > I would also add.. A comment was made about performance. The latest
> > version of saslauthd (v2) supports a caching layer that makes a HUGH
> > difference in speed. We allow credentials to be cached for 1 hour which
> > means only 1 TGT request gets generated each hour then saslauthd caches
> > the results. If you support lots of simple binds via saslauthd
> > (protected by SSL of course) or Cyrus IMAP connections via SSL like we
> > do it makes a BIG difference.
>
> Does this happen by default or is it configurable somewhere?  This
> could help us a lot.
>

It does not happen by default.  For more

man saslauthd

-- 
Igor

References:
- Re: kpasswd
  - From: Allan Streib <astreib@indiana.edu>

Prev by Date: Re: kpasswd
Next by Date: Re: kpasswd
Index(es):
- Chronological
- Thread