Pablo, You were right, when I ran AuthorizeWcfServices.bat, I only added permissions to the Certs for my local user account. After deleting and running again granting permission to /Everyone it worked.
Thanks, I'll check STONEHENGE-109 in now. Can you update the WIKI with the new instructions. -Ben Dewey -----Original Message----- From: Pablo Cibraro [mailto:[email protected]] Sent: Tuesday, December 08, 2009 9:29 AM To: [email protected] Subject: RE: [jira] Created: (STONEHENGE-109) WIF RC Support for .NET Implementation Ben, At first glance, it looks to me like an issue with the certificates. The passive STS can not find some certificate or it does not have permissions to read the private key. Could you check that all the certicates are correctly installed, and the ASP.NET account has the right permissions over the private's keys ? Thanks Pablo. -----Original Message----- From: Ben Dewey [mailto:[email protected]] Sent: Tuesday, December 08, 2009 1:22 AM To: [email protected] Subject: RE: [jira] Created: (STONEHENGE-109) WIF RC Support for .NET Implementation Pablo, Long story short, I went to install WIF RC, but the Beta2 build of Win2008R2 I was running isn't supported. I had to rebuild my entire VM. I got it installed and running, but I'm receiving an error after logging into the IDP. Keyset does not exist -------------------- Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Security.Cryptography.CryptographicException: Keyset does not exist Source Error: Line 48: { Line 49: SecurityTokenService sts = new CustomSecurityTokenService(CustomSecurityTokenServiceConfiguration.Current); Line 50: SignInResponseMessage responseMessage = FederatedPassiveSecurityTokenServiceOperations.ProcessSignInRequest(requestMessage, User, sts); Line 51: FederatedPassiveSecurityTokenServiceOperations.ProcessSignInResponse(responseMessage, Response); Line 52: } I may have glossed over something in the reinstallation/configuration, but it's getting late for me and my brain can't pin-point the issue. Any help would be appreciated, so I can commit this STONEHNEGE-109 patch. -Ben Dewey
