You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've read the documentation about claim resolvers. It is quite clear that for a relying party technical profile, we should only add an output claim "tenantId" with its default value set to "{Policy:TenantObjectId}" and AlwaysUseDefaultValue="true". That's what's in your starter pack. Her's my custom policy relying party :
But unfortunately, here's what my access token get: "tid": "{Policy:TenantObjectId}",
So it seems the claim resolver doesn't work in relying parties (it works in a self asserted technical profile for the same policy) . Or did I forget something here? Both the doc and your samples specifies there is no need for the Metadata item "IncludeClaimResolvingInClaimsHandling" here.
The text was updated successfully, but these errors were encountered:
I've read the documentation about claim resolvers. It is quite clear that for a relying party technical profile, we should only add an output claim "tenantId" with its default value set to "{Policy:TenantObjectId}" and AlwaysUseDefaultValue="true". That's what's in your starter pack. Her's my custom policy relying party :
But unfortunately, here's what my access token get:
"tid": "{Policy:TenantObjectId}",
So it seems the claim resolver doesn't work in relying parties (it works in a self asserted technical profile for the same policy) . Or did I forget something here? Both the doc and your samples specifies there is no need for the Metadata item "IncludeClaimResolvingInClaimsHandling" here.
The text was updated successfully, but these errors were encountered: