Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5A2CD18C76 for ; Fri, 7 Aug 2015 20:41:54 +0000 (UTC) Received: (qmail 64664 invoked by uid 500); 7 Aug 2015 20:41:46 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 64596 invoked by uid 500); 7 Aug 2015 20:41:46 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 64583 invoked by uid 99); 7 Aug 2015 20:41:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Aug 2015 20:41:46 +0000 Date: Fri, 7 Aug 2015 20:41:46 +0000 (UTC) From: "lucas theisen (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DIRSERVER-2088) Add the ability to specify additional fields that should be hashed by the hashing interceptors MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DIRSERVER-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662405#comment-14662405 ] lucas theisen commented on DIRSERVER-2088: ------------------------------------------ A little deeper investigation yeilds these nuggets of information: # All the OID's are defined in {{api-ldap-schema-data}} # Apache Directory OID's have a base of {{1.3.6.1.4.1.18060.0.4.1}} ## {{.0}}: {{ou=syntaxes}} _and_ {{ou=syntaxCheckers}} ### {{ou=syntax}} has the same OID as the associated {{ou=syntaxChecker}} ## {{.1}}: {{ou=comparators}} _and_ {{ou=matchingRules}} _and_ {{ou=normalizers}} ### _not sure what ties the 3 together_ ## {{.2}}: {{ou=attributeTypes}} ### _seems to have some major jumps in sequence... possible sub-grouping by 100's, though looks inconsistent_ ## {{.3}}: {{ou=objectClasses}} ### _seems to have some major jumps in sequence... possible sub-grouping by 100's, though looks inconsistent_ > 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 > > 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)