#2508 DelegateISE token - RFC822Name in the SAN pattern does not reflect in the auth certificate
Closed: Invalid Opened by rpattath.

DelegateISE token - RFC822Name in the SAN pattern does not reflect in the auth
certificate

Steps to Reproduce:

1. DelegateISE config changes are made, TPS CS. cfg has the following changes
as well
op.enroll.delegateISEtoken.keyGen.authentication.SANpattern=$auth.RFC822Name$
auths.instance.ldap1.ldapStringAttributes=mail,cn,uid,edipi,pcc,firstname,lastn
ame,exec-edipi,exec-pcc,exec-mail,certsToAdd,tokenCUID,tokenType,RFC822Name
2. The ldap entry looks as follows
dn: uid=delegate1,ou=People,dc=pki-tps1
objectClass: person
objectClass: organizationalPerson
objectClass: inetorgperson
objectClass: top
objectClass: extensibleobject
cn: delegate1
sn: delegate1
uid: delegate1
givenName: delegate1
mail: johndoe@EXAMPLE.ORG
firstname: John
lastname: Doe
memberid: 7654321
catcode: AC
edipi: 123456789
edipi: 999999999
pcc: AA
exec-memberid: 1234567
exec-catcode: AC
exec-mail: exec1@EXAMPLE.ORG
userPassword:: e1NTSEF9NHBlTVJqNlN5WFY1QSs0WTVEdktKSXB0b3k4TEtUd2lmclpuNmc9PQ=
 =
tokenType: delegateISEtoken
certstoadd: 268435509,ca1,57,kra1
exec-edipi: 12345
rfc822name: delegate1@example.org
3. Enroll a token

Actual results:

The authentication cert on the token has the following
Identifier: Subject Alternative Name - 2.5.29.17
                    Critical: no
                    Value:
                        OtherName:
(UTF8String)1.3.6.1.4.1.311.20.2.3,$auth.RFC822Name

Per PKI Bug Council of 10/18/2016:

Roshni retested and could not reproduce. Not a bug

Metadata Update from @rpattath:
- Issue set to the milestone: 10.3.6

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2628

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata