New answers tagged iis
In this case, the account you're connecting with will be the machine account, because the web application is likely running under the context of either: The Network Service account The AppPoolIdentity account. In either case they're limited non-interactive accounts, and since the application is already running under the context of one of these ...
If your web app is compromised the attacker will normally get the same privileges as the user running the application. From what it sounds like that would be a domain user. Also, it sounds like they would have read and WRITE access to your database. Depending on what's in there you may not want that.
I solved the problem. I installed the WinHttpCertCfg tool and granted access to the private key. The command that worked for me is: WinHttpCertCfg.exe -g -c LOCAL_MACHINE\MY -s "" -a EVERYONE
When the machine says that "you have the private key corresponding to this certificate", then this means that you have the private key which corresponds to the certificate, not that the certificate itself contains the private key. Asymmetric keys come in pairs: the public key and the private key. They are mathematically linked to each other, but rebuilding ...
Top 50 recent answers are included