[
https://issues.apache.org/jira/browse/DIRSERVER-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698168#comment-14698168
]
Emmanuel Lecharny commented on DIRSERVER-2088:
----------------------------------------------
Hi Lucas,
- The default value is rarely needed. If you check the code, it's mainly used
by the {{JdbmIndexBean}}, {{JdbmPartitionBean}}, {{PasswordPolicyBean}} and
{{TransportBean}}. If you don't need a default value, ignore it.
- There is no reason to have multiple interceptor to do the same thing :-) so,
yes, a replacement would make sense. Although one important point is the impact
to our courrent users : if we have to change the config, that means users will
have to do that. What would be the best path to make it easy for them ? We also
need to change Studio GUI in order to take care of that.
- I would rather use something like {{m-oid=1.3.6.1.4.1.18060.0.4.1.2.132}} and
{{m-oid=1.3.6.1.4.1.18060.0.4.1.2.133}} for the two attributeTypes. No need to
add a new level, atm. But it's really cosmetic at this point.
- AFAICT, only one hash method will be available. Is that correct ? I was
wondering if one want to hash some AT using hash algorithm X and some other AT
with hash algorithm Y, then how would we handle this use case ? (not sure it
worth bothering actually).
Thanks Lucas
> 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/%3cbn1pr09mb019635837eb5b0c564a0e955cd...@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)
