Testcafe: Client Certificate Authentication

[snowl]

Are you requesting a feature or reporting a bug?

Requesting a feature

What is the current behavior?

Connecting to a website that uses client certificate authentication doesn't authenticate the user (or even show the prompt for the client certificate authentication).

What is the expected behavior?

You should be able to connect to a server that uses client certificate authentication (either by specifying a certificate to load within the test, like HTTP Authentication, or at least showing the prompt to the user).

How would you reproduce the current behavior (if this is a bug)?

Connect to any server that requires client certificate authentication. The browser will not show any prompts to select the user certificate to use, and all requests will show as a 403 through hammerhead.

Specify your

• operating system: Fedora 24
• testcafe version: 0.18.6
• node.js version: 8.9.4

[miherlosev]

Hi @snowl
Thanks for your proposal.
When the Request Hooks Feature will be implemented, it will be possible to use Client Sertificate Autentification in tests. I'll create an example.

For myself: the detailed article about 'Client Sertificate Autentification' in nodejs.

[BobLuursema]

+1

[snowl]

Hi @miherlosev,

Since request hooks has been merged into the alpha and you have added docs for Request Hooks (#2309), are you able to add documentation to enable Client Certificate Authentication within the docs as well?

Thanks

[stale[bot]]

This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.

[stale[bot]]

We're closing this issue after a prolonged period of inactivity. If it still affects you, please create a new issue with up-to-date information. Thank you.