[jira] Updated: (DIRKRB-16) Encapsulate configuration managment

["Emmanuel Lecharny (JIRA)" <ji...@apache.org>]

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

Emmanuel Lecharny updated DIRKRB-16:
------------------------------------

    Affects Version/s: 2.0.0-RC1

> Encapsulate configuration managment
> -----------------------------------
>
>                 Key: DIRKRB-16
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-16
>             Project: Directory Kerberos
>          Issue Type: New Feature
>    Affects Versions: 2.0.0-RC1
>            Reporter: Enrique Rodriguez
>            Assignee: Enrique Rodriguez
>            Priority: Minor
>
> 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.