Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GeneralName doesn't support otherName #534

Closed
rarf opened this issue Jan 28, 2022 · 2 comments
Closed

GeneralName doesn't support otherName #534

rarf opened this issue Jan 28, 2022 · 2 comments

Comments

@rarf
Copy link

rarf commented Jan 28, 2022

KJUR.asn1.x509.GeneralName doesn't support otherName

GeneralName ::= CHOICE {
otherName [0] OtherName,
rfc822Name [1] IA5String,
dNSName [2] IA5String,
x400Address [3] ORAddress,
directoryName [4] Name,
ediPartyName [5] EDIPartyName,
uniformResourceIdentifier [6] IA5String,
iPAddress [7] OCTET STRING,
registeredID [8] OBJECT IDENTIFIER }

@kjur
Copy link
Owner

kjur commented Jan 28, 2022

OtherName ::= SEQUENCE {
        type-id    OBJECT IDENTIFIER,
        value      [0] EXPLICIT ANY DEFINED BY type-id }

OtherName value includes ANY. Sorry but there is no plan to support OtherName at this stage.

@rarf
Copy link
Author

rarf commented Jan 28, 2022

I sent a pull request #535 my approach is to use ASN1Util.newObject so the developer can pass any ASN1Object, this would simplify my PKCS#10 with otherName generations, to do that now i need to create all the SubjectAltName manualy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants