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

feat: Support PEM certificates for ClientCertificateAuthentication #4473

Merged
merged 1 commit into from
Feb 7, 2024

Conversation

marikaner
Copy link
Contributor

@marikaner marikaner commented Feb 6, 2024

Currently I am using the whole file for both the key and certificate. That way we don’t have to parse the content of the certificate and it seems that the https agent can parse it on its own.

Closes https://github.com/SAP/cloud-sdk-backlog/issues/1178.

Copy link
Member

@tomfrenken tomfrenken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just a minor suggestion

pfx?: Buffer;
passphrase?: string;
}
| {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently, every single parameter is optional, if one of the two options is chosen, isn't every single parameter required? Or can you have e.g. a pfx cert without passphrase or cert & key but no passphrase?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might even create a type for these two objects to make it a little more concise in the function API.

@marikaner marikaner merged commit 36be489 into main Feb 7, 2024
13 of 14 checks passed
@marikaner marikaner deleted the pem branch February 7, 2024 08:46
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

Successfully merging this pull request may close these issues.

2 participants