You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/pages/tutorials/advanced/configuressl/configuressl.rst
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,13 @@
3
3
Configuring SSL in Hoverfly
4
4
===========================
5
5
6
+
Hoverfly supports both one-way and two-way SSL authentication.
7
+
8
+
Hoverfly uses default certificate which you should add to your HTTPS client's trust store for one-way SSL authentication. You have options to provide your own certificate, please see below.
9
+
10
+
Override default certificate for one-way SSL authentication
In some cases, you may not wish to use Hoverfly's default SSL certificate. Hoverfly allows
7
14
you to generate a new certificate and key.
8
15
@@ -26,3 +33,18 @@ to start an instance of Hoverfly using these files.
26
33
27
34
.. note::
28
35
Both a certificate and a key file must be supplied. The files must be in unencrypted PEM format.
36
+
37
+
38
+
Configure Hoverfly for two-way SSL authentication
39
+
-------------------------------------------------
40
+
41
+
For two-way or mutual SSL authentication, you should provide Hoverfly with a client certificate and a certificate key that you use to authenticate with the remote server.
42
+
43
+
Two-way SSL authentication is only enabled for request hosts that match the value you provided to the ``--client-authentication-destination`` flag. You can also pass a regex pattern if you need to match multiple hosts.
44
+
45
+
.. code:: bash
46
+
47
+
hoverctl start --client-authentication-client-cert cert.pem --client-authentication-client-key key.pem --client-authentication-destination <host name of the remote server>
48
+
49
+
50
+
If you need to provide a CA cert, you can do so using the ``--client-authentication-ca-cert`` flag.
0 commit comments