[
https://issues.jboss.org/browse/ELY-745?page=com.atlassian.jira.plugin.sy...
]
Jan Kalina edited comment on ELY-745 at 11/15/16 4:50 AM:
----------------------------------------------------------
[~dlofthouse]:
??I think when we talked previously an option was to create a properties file with all the
OIDs as a database, they could then be classified and used in different situations.??
How do you mean "be classified" ? The OIDs should not be in collision even
without categories. By which it should be categorized/classified?
Would you agree with following property file format?
{code:java}
2.5.4.4=sn,surname
2.5.4.3=cn,commonName
{code}
(first name would be primary - would by used for OID to name conversion, the others would
be used for name to OID conversion only)
Should this property file replace current X500 class of constants?
was (Author: honza889):
[~dlofthouse]:
??I think when we talked previously an option was to create a properties file with all the
OIDs as a database, they could then be classified and used in different situations.??
How do you mean "be classified" ? The OIDs should not be in collision even
without categories.
Would you agree with following property file format?
{code:java}
2.5.4.4=sn,surname
2.5.4.3=cn,commonName
{code}
(first name would be primary - would by used for OID to name conversion, the others would
be used for name to OID conversion only)
Should this property file replace current X500 class of constants?
Using attribute name instead of OID in
x500-attribute-principal-decoder
-----------------------------------------------------------------------
Key: ELY-745
URL:
https://issues.jboss.org/browse/ELY-745
Project: WildFly Elytron
Issue Type: Bug
Components: X.500
Reporter: Jan Kalina
Assignee: Jan Kalina
Priority: Critical
Using OIDs not really convenient.
See description of JBEAP-6100 for more details.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)