starred/WireMock.Net-wiremock
1
0
Fork 0
mirror of https://github.com/wiremock/WireMock.Net.git synced 2026-03-22 09:09:02 +01:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

Updated Using HTTPS (SSL) (markdown)

Stef Heyenrath
2020-10-11 11:39:06 +02:00
parent 8f930b6d56
commit c244d84e33
1 changed files with 62 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

65
Using-HTTPS-(SSL).md

@@ -1,4 +1,4 @@
### HTTP (SSL)
# HTTP (SSL)
You can start a standalone mock server listening for HTTPS requests. To do so, there is just a flag to set when creating the server:
```csharp
var server1 = WireMockServer.Start(port: 8443, ssl: true);
@@ -11,6 +11,65 @@ var server2 = WireMockServer.Start(new FluentMockServerSettings
});
```
- In case when using **net 4.5.2** or **net 4.6**, you need a certificate registered on your box, properly associated with your application and the port number that will be used. This is not really specific to WireMock.Net, not very straightforward and hence the following stackoverflow thread might come handy: [Httplistener with https support](http://stackoverflow.com/questions/11403333/httplistener-with-https-support).
## Windows
### .NET Standard / .NET Core
In case you don't have a self-signed certificate yet, run the following command:
``` cmd
dotnet dev-certs https --trust
```
- When using **netstandard**, WireMock.Net uses a self signed certificate (which can be overriden if you like) to host https urls.
WireMock.Net will now use this self signed certificate (which can be overridden if you like) to host https urls.
### .NET 4.5.2 / .NET 4.6
In case when using .NET 4.5.2 or .NET 4.6, you need a certificate registered on your box, properly associated with your application and the port number that will be used. This is not really specific to WireMock.Net, not very straightforward and hence the following StackOverflow thread might come handy: [Httplistener with https support](http://stackoverflow.com/questions/11403333/httplistener-with-https-support).
## Linux
In case of Linux or running WireMock.Net inside a Linux Docker container, apply the next steps:
1. Make the `localhost.conf` file of content:
``` ini
[req]
default_bits = 2048
default_keyfile = localhost.key
distinguished_name = req_distinguished_name
req_extensions = req_ext
x509_extensions = v3_ca
[req_distinguished_name]
commonName = Common Name (e.g. server FQDN or YOUR name)
[req_ext]
subjectAltName = @alt_names
[v3_ca]
subjectAltName = @alt_names
basicConstraints = critical, CA:false
keyUsage = keyCertSign, cRLSign, digitalSignature,keyEncipherment
extendedKeyUsage = 1.3.6.1.5.5.7.3.1
1.3.6.1.4.1.311.84.1.1 = DER:01
[alt_names]
DNS.1 = localhost
DNS.2 = 127.0.0.1
```
Note the `1.3.6.1.4.1.311.84.1.1 = DER:01` it is critical for aspnet for [recognizing](https://github.com/dotnet/aspnetcore/blob/c75b3f7a2fb9fe21fd96c93c070fdfa88a2fbe97/src/Shared/CertificateGeneration/CertificateManager.cs#L81) the cert.
2. Generate the cert:
``` sh
openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout localhost.key -out localhost.crt -config localhost.conf -subj /CN=localhost
openssl pkcs12 -export -out localhost.pfx -inkey localhost.key -in localhost.crt -passout pass:
```
3. Grab the `localhost.pfx` and `localhost.crt` and copy these files into the target system. In case of `Docker` that would look:
``` dockerfile
COPY localhost.crt /usr/local/share/ca-certificates/
RUN dotnet dev-certs https --clean \
&& update-ca-certificates
COPY localhost.pfx /root/.dotnet/corefx/cryptography/x509stores/my/
```
4. Profit. The system has the aspnetcore dev cert trusted.
See also this [wiremock.net-https-demo-project](https://github.com/winseros/wiremock.net-https-demo-project).