I have a custom STS built with Geneva FX beta 1. Aside from the welcome scope constructor changes I have one outstanding problem, generating display claims. The STS issues a few custom claims, and some of the standard ones. What I had done in beta 1 was the following

switch (claim.ClaimType)
{
case WSIdentityConstants.ClaimTypes.PPID:
DisplayClaim ppidClaim =
this.SecurityTokenServiceConfiguration.ClaimMapper.GetDisplayClaimFromClaim(
claim,
requestedDisplayTokenLanguage,
out actualLanguage);

displayClaim =
new DisplayClaim(
WSIdentityConstants.ClaimTypes.PPID,
ppidClaim.DisplayTag,
ppidClaim.Description,
GetFriendlyIdentifier(claim.Value));
break;

default:
displayClaim =
this.SecurityTokenServiceConfiguration.ClaimMapper.GetDisplayClaimFromClaim(
claim,
requestedDisplayTokenLanguage,
out actualLanguage);
break;
}

Now I discover ClaimMapper is gone, so I can't build the standard ones like I had done. So where is it hiding? I can't find a way to hook into the default display claim stuff to pull the built in names out.

DisplayClaim has a static method

public static DisplayClaim CreateDisplayClaimFromClaimType(string claimType)

---

Dominick Baier | thinktecture | http://www.leastprivilege.com

DisplayClaim has a static method

public static DisplayClaim CreateDisplayClaimFromClaimType(string claimType)

---

Dominick Baier | thinktecture | http://www.leastprivilege.com

Ah great. Interesting that no longer takes a language, I wonder if language support has been dropped. Also it's a darned shame it doesn't take a claim itself any more, now I have two steps to go through, create a temporary display claim, then add the value.

Guys could we get a method that takes a claim as well?