You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Enrique Rodriguez (JIRA)" <ji...@apache.org> on 2004/12/07 03:40:13 UTC
[jira] Created: (DIRKERBEROS-18) Encapsulate configuration managment
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
Assigned to: 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.
-
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
[jira] Updated: (DIRKERBEROS-18) Encapsulate configuration managment
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ 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