-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
Overriding the default ssl certificate via file. #536
Comments
Hello @adusak, are you running WireMock.Net as C# in your unit-tests? Or do you use a separate Docker instance? |
Hey, I am using it in C# unit tests. |
Hi @adusak, I've created a fix based on this article: https://devblogs.microsoft.com/aspnet/configuring-https-in-asp-net-core-across-different-platforms/ I've added a new property |
Sorry, please use MyGet version See : https://github.com/WireMock-Net/WireMock.Net/wiki/MyGet-preview-versions |
Wow, nice! It works like a charm 🙂 I was actually thinking of doing a PR with something along those lines if the config was missing. |
If you install version (needed in case you have multiple |
@adusak Can you do a last final test ? |
Tested with the |
Code is merged to master. A new official NuGet will be ready soon. |
Hey, I have a question regarding the configuration of SSL certificate.
As I understand WireMock used to ship with a custom self-signed which was used when setting up https endpoints.
Sice .NET Core 3 it relies on the dev certificate created by the SDK toolkit.
My question is whether it is possible to override this configuration a use a custom ssl certificate from a file.
My use-case is for example is CI. We run some builds on build agents but not all of them are correctly configured with the dev certificate. So some of the unit tests can fail. I would like to be able to remove the dependency on the environment and be able to configure the SSL certificate from a file - since importing to cert store is out of the question on the build agent.
Is there some settings I am overlooking?
Thank you for your time and an awesome nuget!
The text was updated successfully, but these errors were encountered: