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 read article of Steve Peshka here which points that we have to develop custom claims provider in order to override pepole searching using people picker in SP2010.

I have two questions regarding this approach.

Firstly, If we hook our custom claims provider to trusted identity token issuer, how augmented claims will be encoded? Will it be as they were coming from trusted token issuer (eg. c:0ǹ.t|adfs|<claimValue>) or as they would be coming from custom claim provider (eg. c:0ǹ.c|customclaimprovider|<claimValue>)?

Secondly, when we attach custom claims provider to token issuer, is there any reference available to that token issuer?

share|improve this question
up vote 2 down vote accepted
  1. Your code needs to create the claim, and you specify the original issuer in the constructor. Steve wrote about this too.

  2. The claim provider does not know about the login provider (token issuer). Since you will already have the login provider name (needed to issue the appropriate identity claim), you can get the login provider from the SPSecurityTokenServiceManager

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.