directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DIRKERBEROS-18) Encapsulate configuration managment
Date Thu, 09 Dec 2004 18:20:26 GMT
     [ http://nagoya.apache.org/jira/browse/DIRKERBEROS-18?page=history ]

Alex Karasulu updated DIRKERBEROS-18:
-------------------------------------

    Fix Version: 0.4.0

> Encapsulate configuration managment
> -----------------------------------
>
>          Key: DIRKERBEROS-18
>          URL: http://nagoya.apache.org/jira/browse/DIRKERBEROS-18
>      Project: Kerberos
>         Type: New Feature
>   Components: Configuration Manager
>     Reporter: Enrique Rodriguez
>     Assignee: Enrique Rodriguez
>     Priority: Minor
>      Fix For: 0.4.0

>
> The various Kerberos schemas specify configuration at a number of levels, such as per
Client, per Realm, and per KDC, and across a number of configuration options.  This configuration
will come from the file system or the Eve backing store.  In order to hide the resulting complexity
from the KDC services, we'll encapsulate this logic in a Configuration Manager and expose
it to the KDC services using the Java Preferences API.
> Some examples of configuration options are:
> Per encryption system secret key
> Secret key expiration
> Minimum supported lifetime
> Maximum renewable lifetime (renewtill - starttime)
> Maximum allowable lifetime (endtime - starttime)
> allow empty address fields
> allow proxiable ticket requests
> allow forwardable ticket requests
> allow renewable ticket requests
> allow postdated ticket requests

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message