[
https://issues.apache.org/jira/browse/DIRKRB-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588864#comment-14588864
]
Stefan Seelmann commented on DIRKRB-293:
----------------------------------------
Thank for the update patches, I like them.
Haha, I totally missed that you store keykvno into givenName ;). I'm not an
expert at all in the topic, but I think the krb5* objectclasses and attributes
that are supported in ApacheDS are based on some old draft and are not
standardized in an RFC and thus we can't expect that any other LDAP server
knows it. If this backend should work with any LDAP server then I'd suggest to
define a new schema and ship it with Kerby and document that it needs to be
added into the used LDAP server. To define your own schema you can use
ApacheDirctoryStudio, it has a schema editor to define a schema with
objectclasses and attributes. However this needs to be done carefully,
especially to avoid name clashes and to use the right OID assignments
(https://cwiki.apache.org/confluence/display/DIRxPMGT/OID+Assignment+Scheme).
[~elecharny] [~akiran] Any comments from you?
> 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)
