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] [Commented] (DIRSERVER-2088) Add the ability to specify additional fields that should be hashed by the hashing interceptors
Date Fri, 07 Aug 2015 22:03:46 GMT

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

Emmanuel Lecharny commented on DIRSERVER-2088:
----------------------------------------------

OID are not semantically very significant :/

So we had to pick numbers for AT, OC and other elements. As you already realized, AT and OC
OID are predefined, at least for all there number but the last one. So it will be {{abc.2.xxx}}
for an AT and {{abc.3.yyy}} for an OC.

* OCs

0 is for the base bean
100 is for the directory service and the underlying elements : 130, here, is for interceptors
(and 131, 132, ... up to 139 are the actual specific interceptors).
300 is for the LdapServer
400 is for the Kerberos Server
500 is for the DNS server
600 is for the DHCP server
700 is for the NTP server
800 is for the ChangePassword server
900 if for the PPolicy

* For the AT :
The logic is pretty much teh same, so in yoru case, you should pick an AT oid with finish
by 132 plus a postfix (132 for the HashingInterceptor OC, and 132.1 for its first AT, 132.2
for teh second one, etc) 

> Add the ability to specify additional fields that should be hashed by the hashing interceptors
> ----------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-2088
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-2088
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: lucas theisen
>         Attachments: oid_map.json, oid_map.pl
>
>
> This [discussion|http://mail-archives.apache.org/mod_mbox/directory-dev/201507.mbox/%3CBN1PR09MB019635837EB5B0C564A0E955CD820@BN1PR09MB0196.namprd09.prod.outlook.com%3E]
went over the topic.  Per the suggestion from [~akiran], this should be done with some new
attributes:
> {quote}
> what I would do is to add support for configuring one or more attributes in
> this interceptor
> something like, 'ads-hashAttibute' a multi valued attributes
> {quote}
> Per [~elecharny], a new {{objectClass}} should be created:
> {quote}
> The idea is to add some configuration in the HashInterceptor
> configuration. You can create a new ObjectClass for that and add some
> new AttributeType to store the OID to be hashed.
> {quote}
> And given that we will create a new {{objectClass}} with its own configuration attribute
for {{ads-hashAttribute}} it is also reasonable to add {{ads-hashAlgorithm}}.  With this,
_ALL_ of the individual classes could be implemented as one simple {{HashingInterceptor}}.



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

Mime
View raw message