[jira] [Updated] (DIRSERVER-2164) "certificateExactMatch (This matching rule doesnt exist)" when importing schema
[ https://issues.apache.org/jira/browse/DIRSERVER-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lecharny updated DIRSERVER-2164: - Component/s: schema > "certificateExactMatch (This matching rule doesnt exist)" when importing > schema > --- > > Key: DIRSERVER-2164 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2164 > Project: Directory ApacheDS > Issue Type: Bug > Components: schema >Affects Versions: 2.0.0-M23 > Environment: Linux x 3.10.0-327.28.2.el7.x86_64 #1 SMP Wed Aug 3 > 11:11:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > openjdk version "1.8.0_101" > OpenJDK Runtime Environment (build 1.8.0_101-b13) > OpenJDK 64-Bit Server VM (build 25.101-b13, mixed mode) >Reporter: José Manuel >Priority: Minor > Labels: certificateExactMatch, import, ldap, newbie, schema > > Hi, > not completely sure if this is a bug, sorry... but please read the rest of > the issue description. > I'm having an issue importing an schema. I see it both when I try to import > the schema in Directory Studio, and into an ApacheDS (running 2.0.0-M23) > connected through Directory Studio. > This schema seems to be imported correctly in openldap and 389, and the > definition of the attibute that causes the issue is simmilar to that included > in RFC 4523 section 4.1: > ( 2.5.4.36 NAME 'userCertificate' > DESC 'X.509 user certificate' > EQUALITY certificateExactMatch > SYNTAX 1.3.6.1.4.1.1466.115.121.1.8 ) > My definition of the attribute is: > attributetype ( 1.3.6.1.4.1.7547.4.3.2.4 NAME 'digitalCertificate' > DESC 'RFC2256: X.509 certificate, use ;binary' > EQUALITY certificateExactMatch > SYNTAX 1.3.6.1.4.1.1466.115.121.1.8 ) > What can be wrong? > Thanks, > Jose. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSERVER-2164) "certificateExactMatch (This matching rule doesnt exist)" when importing schema
[ https://issues.apache.org/jira/browse/DIRSERVER-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lecharny updated DIRSERVER-2164: - Fix Version/s: 2.1.0 > "certificateExactMatch (This matching rule doesnt exist)" when importing > schema > --- > > Key: DIRSERVER-2164 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2164 > Project: Directory ApacheDS > Issue Type: Bug > Components: schema >Affects Versions: 2.0.0-M23 > Environment: Linux x 3.10.0-327.28.2.el7.x86_64 #1 SMP Wed Aug 3 > 11:11:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > openjdk version "1.8.0_101" > OpenJDK Runtime Environment (build 1.8.0_101-b13) > OpenJDK 64-Bit Server VM (build 25.101-b13, mixed mode) >Reporter: José Manuel >Priority: Minor > Labels: certificateExactMatch, import, ldap, newbie, schema > Fix For: 2.1.0 > > > Hi, > not completely sure if this is a bug, sorry... but please read the rest of > the issue description. > I'm having an issue importing an schema. I see it both when I try to import > the schema in Directory Studio, and into an ApacheDS (running 2.0.0-M23) > connected through Directory Studio. > This schema seems to be imported correctly in openldap and 389, and the > definition of the attibute that causes the issue is simmilar to that included > in RFC 4523 section 4.1: > ( 2.5.4.36 NAME 'userCertificate' > DESC 'X.509 user certificate' > EQUALITY certificateExactMatch > SYNTAX 1.3.6.1.4.1.1466.115.121.1.8 ) > My definition of the attribute is: > attributetype ( 1.3.6.1.4.1.7547.4.3.2.4 NAME 'digitalCertificate' > DESC 'RFC2256: X.509 certificate, use ;binary' > EQUALITY certificateExactMatch > SYNTAX 1.3.6.1.4.1.1466.115.121.1.8 ) > What can be wrong? > Thanks, > Jose. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
