[ http://issues.apache.org/jira/browse/DIREVE-300?page=all ]
Alex Karasulu closed DIREVE-300:
--------------------------------
Resolution: Fixed
Fixed this a while back.
> Correct improper format for java.naming.ldap.attributes.binary
> --------------------------------------------------------------
>
> Key: DIREVE-300
> URL: http://issues.apache.org/jira/browse/DIREVE-300
> Project: Directory Server
> Type: Bug
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
>
> Right now we use this format for binary attribute information which is not
> correct.
> <prop
> key="java.naming.ldap.attributes.binary">0.9.2342.19200300.100.1.55/a
> udio/2.5.4.38/authorityRevocationList/2.5.4.37/cACertificate/2.5.4.39/certificateRe
> vocationList/2.5.4.40/crossCertificatePair/2.5.4.53/deltaRevocationList/1.3.6.1.4.1
> .42.2.27.4.1.8/javaSerializedData/0.9.2342.19200300.100.1.60/jpegPhoto/1.3.6.1.4.1.
> 5322.10.1.10/krb5Key/1.3.6.1.4.1.5322.10.1.12/krb5RealmName/0.9.2342.19200300.100.1
> .53/personalSignature/0.9.2342.19200300.100.1.7/photo/2.5.4.52/supportedAlgorithms/
> 2.5.4.36/userCertificate/2.5.4.35/userPassword/2.16.840.1.113730.3.1.216/userPKCS12
> /2.16.840.1.113730.3.1.40/userSMIMECertificate</prop>
> We need to create a place where we can add this info properly within the
> configuration. Then we need to make the server set this property itself
> rather than allow it to be done manually. Also warn the user if user
> provided values are overwritten in the environement.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
