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

Add client certificate authentication #20

Closed
phillee007 opened this issue Feb 3, 2017 · 5 comments · Fixed by #862
Closed

Add client certificate authentication #20

phillee007 opened this issue Feb 3, 2017 · 5 comments · Fixed by #862
Assignees
Labels

Comments

@phillee007
Copy link
Contributor

Is it possible to add this functionality as well? :-)

@StefH
Copy link
Collaborator

StefH commented Feb 3, 2017

I don't know if this is easy. Let me think about this.

@StefH StefH self-assigned this Feb 3, 2017
@StefH StefH added the question label Feb 3, 2017
@phillee007
Copy link
Contributor Author

phillee007 commented Feb 3, 2017 via email

@phillee007
Copy link
Contributor Author

phillee007 commented Jun 10, 2017

Have had a look & I'm not sure it's modelled quite right. Each request mapping gets its own settings for proxy url/cert filename (plus also needs password if specified), so there would be no need to specify them in the mock server general settings (or as command-line args) as they wouldn't be used.
I've cloned the repo & will try it out locally over the next week or so to see what i can do.

UPDATE:
Actually I can see the reason why there are both, but was confused at first.

I've made a few changes to get it working both ways, and will submit a PR within the next week or so

@billybraga
Copy link
Contributor

Was this ever done?

@StefH
Copy link
Collaborator

StefH commented Dec 8, 2022

Sorry.
No this is not implemented.

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

Successfully merging a pull request may close this issue.

3 participants