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
{{ message }}
This repository has been archived by the owner on Dec 14, 2017. It is now read-only.
I've been plugging away at this issue for a bit now. I have a claim that regardless of what scope I add the claim to, is not added to the list of claims for the logged in user using the MVC Form POST example project.
The server sees the need to include the claims (by default they were part of the roles scope, but I've tried other scopes like email). My claim name is superadmin. The JWT when you look at what is posted back to the MVC app contains the superadmin claim. It however isn't parsed.
public class AuthOwin : AuthorizeAttribute
{
protected override bool AuthorizeCore(HttpContextBase httpContext)
{
var e = httpContext.GetOwinContext().Environment.GetIdentityServerFullLoginAsync().Result;
}
}
e.Claims does not contain the super admin claim. It has email, given_name, etc. But not my custom claim.
Suggestions?
The text was updated successfully, but these errors were encountered:
I've been plugging away at this issue for a bit now. I have a claim that regardless of what scope I add the claim to, is not added to the list of claims for the logged in user using the MVC Form POST example project.
The server sees the need to include the claims (by default they were part of the roles scope, but I've tried other scopes like email). My claim name is superadmin. The JWT when you look at what is posted back to the MVC app contains the superadmin claim. It however isn't parsed.
public class AuthOwin : AuthorizeAttribute
{
protected override bool AuthorizeCore(HttpContextBase httpContext)
{
var e = httpContext.GetOwinContext().Environment.GetIdentityServerFullLoginAsync().Result;
}
}
e.Claims does not contain the super admin claim. It has email, given_name, etc. But not my custom claim.
Suggestions?
The text was updated successfully, but these errors were encountered: