MicrosoftI use a custom certificate with WAC and that causes this error in the Application log and the WAC service terminates:
Application: WindowsAdminCenter.exe
CoreCLR Version: 8.0.1024.46610
.NET Version: 8.0.10
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException: The requested certificate CN=servername.local could not be found in LocalMachine/My with AllowInvalid setting: False.
If I use the self-signed certificate the error is not present.
I figured out that what is causing the 'not found' error is that is it looking for the certificate without the X.500 prefix. Do the correct subject in the appsettings.json file should be just 'servername.local' and not 'CN=servername.local'. Once I made this change to my appsettings.json WAC started successfully with my custom certificate.
Same issue here. Literally every time I update WAC, something is broken/doesn't work. This has to be one of the worst QA'd systems they release, yet they intend on it replacing MMC.
There's zero reason anyone should have to be updating json files like this. It's a half baked solution they keep shoving down our throats.
Edit: Your fix didn't work on mine. I'm using an internal CA cert with a different hostname than the server name (wac.contoso.local instead of contosowac01.contoso.local, but with a SAN including the fqdn) and no matter what I put in that json, it won't work. I can get it to run, but the website never comes up.
To manage your Anger. Custom certs should be working, including SAN as all Browser requires. One need to setup permissions of the service to the certificate.
Mind this is the preview blogpost. WAC 2410 release comments have hints how to get this working.
