Home  >  Article  >  Database  >  When use WIF create STS: The certificate's private k

When use WIF create STS: The certificate's private k

WBOY
WBOYOriginal
2016-06-07 15:38:031193browse

The certificate's private key could not be accessed. Ensure the access control list (ACL) on the certificate's private key grants access to the application pool user. Make sure you know under which account your web app is running (do a Res

The certificate's private key could not be accessed. Ensure the access control list (ACL) on the certificate's private key grants access to the application pool user.


Make sure you know under which account your web app is running (do a Response.Write(WindowsIdentity.GetCurrent().Name to find out).This account needs read access to the private key file. I got a security error on the application site due to my certificates being inaccessible by IIS user, something along the lines of ID1039: The certificate’s private key could not be accessed. Ensure the access control list (ACL) on the certificate’s private key grants access to the application pool user.  I found a solution to that problem on the web.  Basically, you have to give READ permission to the group IIS_IUSRS to the files located at%ALLUSERSPROFILE%\Microsoft\Crypto\RSA\MachineKeys.

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn