[
https://issues.apache.org/jira/browse/DIRSERVER-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lucas theisen updated DIRSERVER-2088:
-------------------------------------
Attachment: oid_map.pl
oid_map.json
Attached a script and its output that I used to investigate all the defined OID
values in the {{api-ldap-schema-data}} module. Do we maybe want to include
this information in the README of that module? Maybe a different format like
xml, or html, or markdown?
> 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)
