directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "lucas theisen (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, 14 Aug 2015 17:56:48 GMT

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

lucas theisen commented on DIRSERVER-2088:
------------------------------------------

[~akiran] or [~elecharny], I am a little confused by the {{@ConfigurationElement}} annotation.
 It has a {{default()}} but that appears to only be used by the {{ConfigWriter.addBean(...)}}
and is ignored by the {{ConfigPartitionReader.readConfig(...)}}.  Is this on purpose?  I wanted
to be able to specify default values in my {{HashInterceptorBean}} in the annotations on the
fields.  It seems like the right place to do it.  However, as they are ignored, it doesnt
work.  I understand this bean is just a container for the configuration, and later a factory
(that i havent found yet) will build the instance from the class name in the {{InterceptorBean}},
and that is the actual place i need the values, but it seems like injecting defaults as early
as possible is the right thing to do.  Am I missing something?

> 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