2

How to login in SharePoint site with facebook login. i follow the steps from this site. http://ovaismehboob.wordpress.com/2011/09/07/configuring-facebook-authentication-in-sharepoint-2010/ but there are some errors.

it gives "500 Internal Server Error" when redirected to our SharePoint Site

3
  • Some errors? Please elaborate :) Oct 19, 2013 at 12:23
  • i follow all steps but then after facebook login it gives "keyset does not exist" error Oct 19, 2013 at 12:38
  • i think its certificate issue Oct 19, 2013 at 12:40

2 Answers 2

9
+50

"Keyset does not exist" means you need to give your web application pool identity account access to your certificate. Do this in the Certificates Snap In.

7
  • thanks for the answer, but how do i give access to certificate. there is no way in certificate snap in to give access Oct 21, 2013 at 4:33
  • Load the Snap In in MMC as the Computer Account. Under 'Personal', right click the cert then from All Tasks, select Manage Private Keys.
    – James Love
    Oct 21, 2013 at 8:04
  • yes, this problem is solved. but now it gives 500 Internal server error Oct 21, 2013 at 9:06
  • Debug with Visual Studio now, as now it smells like a problem in your code behind.
    – James Love
    Oct 21, 2013 at 11:00
  • 2
    Check if the STS is working fine . Try this - Browse to go to IIS Manager --> Sites --> SharePoint WebServices --> SecurityTokenServiceApplication, click on 'Content View' down at the bottom, right click on Securitytoken.svc and click Browse . The expected page of STS should be displayed.
    – Nikhil J
    Oct 21, 2013 at 17:49
3

I had faced the similar issue when i was working with STS. The reason you get the error is because there is no trust being established between the Sharepoint and STS . If i am not wrong you might be getting the error at the below lines of code :) This is definitely a certificate issue.

                SecurityTokenService sts = new CustomSecurityTokenService(CustomSecurityTokenServiceConfiguration.Current);
                SignInResponseMessage responseMessage = FederatedPassiveSecurityTokenServiceOperations.ProcessSignInRequest(requestMessage, User, sts);

Make sure the app pool account which is running the STS code had permissions to access the certificates (STSTestCert) . The Identity of the App Pool the Custom STS is running under .Give the Identity read access to the private key of the certifcate used to encypt the SAML token.

The permissions can be added using the certificate MMC snap-in.

2.If doesnt work the STSTestCert might be corrupt or not accessible .Follow http://discusscode.blogspot.com/2012/01/keyset-does-not-exist-issue-in-creating.html, delete the trust and again try adding the AuthProvider using powershell script.

5
  • yes this problem was solved, but after this, it gives 500 internal server erro Oct 22, 2013 at 4:17
  • Check if the STS is working fine . Try this - Browse to go to IIS Manager --> Sites --> SharePoint WebServices --> SecurityTokenServiceApplication, click on 'Content View' down at the bottom, right click on Securitytoken.svc and click Browse . The expected page of STS should be displayed.
    – Nikhil J
    Oct 22, 2013 at 13:26
  • its working , i already checked that Oct 22, 2013 at 13:28
  • Is the user present in Sharepoint Group with some permissions ? It might be throwing forbidden error.
    – Nikhil J
    Oct 22, 2013 at 13:49
  • no, its 500 Internal server error Oct 23, 2013 at 4:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.