Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 100392 - CRL support in LDAP module
CRL support in LDAP module
Product: Stronghold Cross Platform
Classification: Retired
Component: mod_authz_ldap (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Joe Orton
Stronghold Engineering List
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2003-07-21 18:39 EDT by Lorrayne Schaefer
Modified: 2007-04-18 12:55 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-05 10:07:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lorrayne Schaefer 2003-07-21 18:39:36 EDT
Chris Runge asked me to open a formal Request For Enhancement (RFE) in this area for consideration in a future version of the 

Here's what I'm thinking for CRL support (this is a bit beyond the mod_authz_ldap module, but some of Chris' questions extend to 
the web server):

* Server periodically fetches the CRL (the times for fetching of the CRL is a configurable option in the config file).
* The CRL is cached locally for perfomance.
* Have a configurable option in the config file that specifies what format the CRL is stored in the directory (default format is DER)
* Provide a configurable CRL grace period that will extend beyond the CRL's NextUpdate in either seconds or minutes.  Please 
make this a long interger. 
*  Provide support in following the CRL Distribution Point (if present in the End Entity or CA certificate)
* For CRL retrieval, allow support for ldap://, http://, https://, and file://.
Comment 1 Joe Orton 2006-09-05 10:07:21 EDT
Stronghold 4.0 Cross Platform reached End of Life as of the end of December 2005.

For more information or further options see: 


Note You need to log in before you can comment on or make changes to this bug.