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-158) Implement realm catalog
Date Wed, 09 Jul 2008 12:43:31 GMT

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

Emmanuel Lecharny updated DIRSERVER-158:
----------------------------------------

    Fix Version/s: 2.0.0

postponed

> Implement realm catalog
> -----------------------
>
>                 Key: DIRSERVER-158
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-158
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>          Components: kerberos
>            Reporter: Enrique Rodriguez
>            Assignee: Enrique Rodriguez
>             Fix For: 2.0.0
>
>
> DNS RFC 1035 6.1.2 describes a "catalog" that contains pointers to zone data.  The same
configuration mechanism makes sense for Kerberos so we will implement a realm catalog and
ensure that DNS zone and Kerberos realm semantics are similar.
> o apache.schema objectClass called apachedsServiceConfiguration
> o STRUCTURAL objectClass MUST cn
> o uses ExtensibleObject
> o apacheKerberosConfiguration extends apacheServiceConfiguration
> o OC apacheCatalogEntry is a mapping of a realm name attribute to a zoneBaseDN attribute
> o name=example.com --> ou=users,dc=example,dc=com
> o put a ou=realms under the configuration for a service instance
> o add OC apacheCatalogEntry's
> o pull all catalog entries into memory with a single level search under ou=realms
> o use the zoneBaseDn with the InitialContextFactory. The nexus will figure out under
what partition it is. 

-- 
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