Hi Michael, I got your issue somedays ago. NET 3.5 SP1 Stack Trace: at .GetServiceCertificate(ServiceElement element) at .LoadConfiguration(ServiceElement element) at .ctor(String serviceName) at .ctor(String issuerName, SigningCredentials signingCredentials, String serviceName) at .ctor(String issuerName) at () in C:\TFSProjects\EManager2\IdentityProvider\DefaultSecurityTokenServiceConfiguration.cs:line 12 at (String args) in C:\TFSProjects\EManager2\IdentityProvider.Host\Program.cs:line 16 at System.AppDomain._nExecuteAssembly(Assembly assembly, String args) at .RunUsersAssembly() at (ExecutionContext executionContext, ContextCallback callback, Object state) at () Michael Any clue as to why it would be different? OS: Windows Server 2008 Enterprise VS Version: Visual Studio 2008 Team Studio. for some reason the this particular certificate is located in "C:\ProgramData\Microsoft\Crypto\Keys\" instead of "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\". After doing some research on previous WCF projects I have done and reading some blogs. The certificate is located in the LocalMachine\Personal(My) Store. The user running the test app (which is me) has permissions to the private key of the certificate. Ensure the access control list (ACL) on the certificate's private key grants access to the application pool user". I am recieving this error message: "The certificate's private key could not be accessed.
0 Comments
Leave a Reply. |