SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have set up and SP 2010 web application with claims based authentication with simple, custom STS. How can I connect another web application to the same STS?

For my first web application I used a sample powershell script, but when I try to reuse it (after changing name, description and realm) of SPTrustedIdentityTokenIssuer, I'm getting New-SPTrustedIdentityTokenIssuer : Exception of type 'System.ArgumentException' was thrown.

Thanks in advance ;)

share|improve this question
up vote 1 down vote accepted

You don't have to reconfigure the SPTrustedIdentityTokenIssuer or create an additional one. Just connecting your other web applications to the same trusted identity provider should do the trick.

share|improve this answer
I don't have to add another realm to my token issuer or something? – jjczopek Oct 17 '11 at 10:28
Problem was with our STS stub which refused to work with two different webapps. Moving too properly configured ADFS 2.0 solved the case. – jjczopek Dec 3 '11 at 2:00

You have to add your custom STS to the new web application in

Central Admin > Application Management > Manage Web Applications

. Then select your new web application and click the Authentication Providers button. Choose your zone to update, and then you should see your custom STS listed in the Claims Authentication Types. After this, you have to add your new site to the realm via PowerShell. Something along the lines of:

$ap = Get-SPTrustedIdentityTokenIssuer -Identity "Your Custom STS"

$uri = new-object System.Uri("")

$ap.ProviderRealms.Add($uri, "")

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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