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.
Secondly, when we attach custom claims provider to token issuer, is there any reference available to that token issuer?