directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DIRSERVER-140) Encapsulate configuration managment
Date Wed, 09 Jul 2008 12:53:31 GMT

     [ https://issues.apache.org/jira/browse/DIRSERVER-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Emmanuel Lecharny updated DIRSERVER-140:
----------------------------------------

    Fix Version/s: 2.0.0

It should be possible to do it for 2.0

> Encapsulate configuration managment
> -----------------------------------
>
>                 Key: DIRSERVER-140
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-140
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>          Components: kerberos
>            Reporter: Enrique Rodriguez
>            Assignee: Enrique Rodriguez
>            Priority: Minor
>             Fix For: 2.0.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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message