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.

Sign up for GitHub

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

Jump to bottom

is any option to post https request with client certificate as pfx and passphrase #492

Open
SSathish89 opened this issue Jul 23, 2024 · 2 comments
Open

is any option to post https request with client certificate as pfx and passphrase #492

SSathish89 opened this issue Jul 23, 2024 · 2 comments

Comments

@SSathish89
Copy link

SSathish89 commented Jul 23, 2024 •
edited
Loading

Kindly suggest any work around to post https request with client certificate as pfx and passphrase
@SSathish89 SSathish89 changed the title is any option to post request with client certificate as pfx and passpharse is any option to post https request with client certificate as pfx and passpharse Jul 23, 2024
@SSathish89 SSathish89 changed the title is any option to post https request with client certificate as pfx and passpharse is any option to post https request with client certificate as pfx and passphrase Jul 23, 2024
@nabetti1720
Copy link
Contributor

Hi @SSathish89 , I have done some research on this issue.

LLRT currently relies on rustls_pemfile crates. A rustls_pemfile crate does not support pfx files, only pem files can be specified. Can we consider the possibility of extracting the desired certificate from a pfx file and using it as a pem file?

https://github.com/awslabs/llrt?tab=readme-ov-file#llrt_extra_ca_certsfile

@richarddavison
Copy link
Contributor

richarddavison commented Sep 20, 2024 •
edited
Loading

@SSathish89 did this solve your problem ☝️?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nabetti1720 @SSathish89 @richarddavison