-
Notifications
You must be signed in to change notification settings - Fork 208
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
feat(x509): Update certificate creation API #2197
feat(x509): Update certificate creation API #2197
Conversation
Signed-off-by: Berend Sliedrecht <[email protected]>
… via the `agent.x509.createCertificate` API where the `subjectPublicKey` is not supplied or equal to the `authorityKey` - allow to create more complex X.509 certificates Signed-off-by: Berend Sliedrecht <[email protected]>
🦋 Changeset detectedLatest commit: ba08279 The changes in this PR will be included in the next version bump. This PR includes changesets to release 15 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
aeb6ea5
to
79dff4e
Compare
@@ -228,6 +311,11 @@ export class X509Certificate { | |||
return certificate.subject | |||
} | |||
|
|||
public get issuer() { | |||
const certificate = new x509.X509Certificate(this.rawCertificate) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we store an instance of the x509 lib cert in this class? I'm not sure on the overhead of parsing
… via the `agent.x509.createCertificate` API where the `subjectPublicKey` is not supplied or equal to the `authorityKey` - allow to create more complex X.509 certificates Signed-off-by: Berend Sliedrecht <[email protected]>
79dff4e
to
ba08279
Compare
dca4fdf
into
openwallet-foundation:main
Update the X.509 certificate creation api to not only create self-signed certs anymore.