[ 
https://issues.apache.org/jira/browse/DIRKRB-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589664#comment-14589664
 ] 

Kiran Ayyagari edited comment on DIRKRB-293 at 6/17/15 11:52 AM:
-----------------------------------------------------------------

There is no standard* schema for storing Kerberos data in LDAP. There are two 
options:

# stick to the schema present in ApacheDS and for other LDAP servers let users 
inject that schema into their servers before integrating with Kerby
# add an additional mapping layer in Kerby to support each popular LDAP server.

IMHO first option is the best, second one is just a waste of time instead the 
data can always be migrated to use ApacheDS schema.

There is one expired 
[draft|http://www.highlandsun.com/hyc/drafts/draft-chu-ldap-kdc-schema-xx.html] 
but ApacheDS has similar but custom schema.


was (Author: akiran):
There is no standard* schema for storing Kerberos data in LDAP. There are two 
options:

# stick to the schema present in ApacheDS and for other LDAP servers let users 
inject that schema into their 
   servers before integrating with Kerby

# add an additional mapping layer in Kerby to support each popular LDAP server.

IMHO first option is the best, second one is just a waste of time instead the 
data can always be migrated to use ApacheDS schema.

There is one expired 
[draft|http://www.highlandsun.com/hyc/drafts/draft-chu-ldap-kdc-schema-xx.html] 
but 
  ApacheDS has similar but custom schema.

> Implementing doUpdateIdentity for LdapIdentityBackend
> -----------------------------------------------------
>
>                 Key: DIRKRB-293
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-293
>             Project: Directory Kerberos
>          Issue Type: Sub-task
>            Reporter: Xu Yaning
>            Assignee: Xu Yaning
>         Attachments: DIRKRB-293-v1.patch, DIRKRB-293-v2.patch
>
>
> Impelment {{doUpdateIdentity}} for {{LdapIdentityBackend}} to update an 
> identity.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to