locked
Second Web App Claims Based Authentication Issue RRS feed

  • Question

  • When setting up a second web app to use ADFS 2.0 with Claims Based Authenticated in my Sharepoint Foundation Farm, I am unable get the second URI to work properly.

    I have added the second provider realm as stated (http://blogs.technet.com/b/speschka/archive/2010/04/27/how-to-create-multiple-claims-auth-web-apps-in-a-single-sharepoint-2010-farm.aspx?CommentPosted=true#commentmessage)

    After I add the second Realm, I get an 500 error when trying to access the second web app.

    I have tried setting up a second URI on the first token issuer and have also created a second token issuer which broke both web apps.

    What happens is the second web app will send you back to https://second.domain.com/adfs/ls and give me the 500 Error after you provide your login.

    Thanks,
    Benjamin Chance

    Tuesday, February 22, 2011 1:29 PM

Answers

  • Found 3 Issues that fixed the problem.

    1. Added HTTP Binding to Web App in IIS

    2. Restarted the ADFS 2.0 Service

    3. Found that Relying Trust Identifiers are Case Sensitive


    Thanks, Benjamin Chance
    • Proposed as answer by V284 Thursday, April 21, 2011 8:32 PM
    • Marked as answer by Hemendra Agrawal Sunday, March 17, 2013 12:51 PM
    Thursday, April 21, 2011 6:57 PM