ASOS - JWT token claims are not visible in decoded token in angular
up vote
0
down vote
favorite
In .net 4.6 I had written a custom jwt token handler and was able to parse the token in client side by using angular-jwt.
However in .Net core and using ASOS I added the same token following lines to the startup.
options.AccessTokenHandler = new JwtSecurityTokenHandler
{
InboundClaimTypeMap = new Dictionary<string, string>(),
OutboundClaimTypeMap = new Dictionary<string, string>()
};
This is the code adding claims.
var identity = new ClaimsIdentity(schemeName, OpenIdConnectConstants.Claims.Name,
OpenIdConnectConstants.Claims.Role);
identity.AddClaim(OpenIdConnectConstants.Claims.Subject, "1");
identity.AddClaim(OpenIdConnectConstants.Claims.Name, userName);
identity.AddClaim(OpenIdConnectConstants.Claims.Role, "Admin");
However on the angular side the decoded token doesn't have all claims. I only see sub, nothing else.
This is my angular code.
var decodedValue = this.jwtHelper.decodeToken(variable.access_token);
Not sure what am I missing.
jwt asp.net-identity openid-connect
add a comment |
up vote
0
down vote
favorite
In .net 4.6 I had written a custom jwt token handler and was able to parse the token in client side by using angular-jwt.
However in .Net core and using ASOS I added the same token following lines to the startup.
options.AccessTokenHandler = new JwtSecurityTokenHandler
{
InboundClaimTypeMap = new Dictionary<string, string>(),
OutboundClaimTypeMap = new Dictionary<string, string>()
};
This is the code adding claims.
var identity = new ClaimsIdentity(schemeName, OpenIdConnectConstants.Claims.Name,
OpenIdConnectConstants.Claims.Role);
identity.AddClaim(OpenIdConnectConstants.Claims.Subject, "1");
identity.AddClaim(OpenIdConnectConstants.Claims.Name, userName);
identity.AddClaim(OpenIdConnectConstants.Claims.Role, "Admin");
However on the angular side the decoded token doesn't have all claims. I only see sub, nothing else.
This is my angular code.
var decodedValue = this.jwtHelper.decodeToken(variable.access_token);
Not sure what am I missing.
jwt asp.net-identity openid-connect
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
In .net 4.6 I had written a custom jwt token handler and was able to parse the token in client side by using angular-jwt.
However in .Net core and using ASOS I added the same token following lines to the startup.
options.AccessTokenHandler = new JwtSecurityTokenHandler
{
InboundClaimTypeMap = new Dictionary<string, string>(),
OutboundClaimTypeMap = new Dictionary<string, string>()
};
This is the code adding claims.
var identity = new ClaimsIdentity(schemeName, OpenIdConnectConstants.Claims.Name,
OpenIdConnectConstants.Claims.Role);
identity.AddClaim(OpenIdConnectConstants.Claims.Subject, "1");
identity.AddClaim(OpenIdConnectConstants.Claims.Name, userName);
identity.AddClaim(OpenIdConnectConstants.Claims.Role, "Admin");
However on the angular side the decoded token doesn't have all claims. I only see sub, nothing else.
This is my angular code.
var decodedValue = this.jwtHelper.decodeToken(variable.access_token);
Not sure what am I missing.
jwt asp.net-identity openid-connect
In .net 4.6 I had written a custom jwt token handler and was able to parse the token in client side by using angular-jwt.
However in .Net core and using ASOS I added the same token following lines to the startup.
options.AccessTokenHandler = new JwtSecurityTokenHandler
{
InboundClaimTypeMap = new Dictionary<string, string>(),
OutboundClaimTypeMap = new Dictionary<string, string>()
};
This is the code adding claims.
var identity = new ClaimsIdentity(schemeName, OpenIdConnectConstants.Claims.Name,
OpenIdConnectConstants.Claims.Role);
identity.AddClaim(OpenIdConnectConstants.Claims.Subject, "1");
identity.AddClaim(OpenIdConnectConstants.Claims.Name, userName);
identity.AddClaim(OpenIdConnectConstants.Claims.Role, "Admin");
However on the angular side the decoded token doesn't have all claims. I only see sub, nothing else.
This is my angular code.
var decodedValue = this.jwtHelper.decodeToken(variable.access_token);
Not sure what am I missing.
jwt asp.net-identity openid-connect
jwt asp.net-identity openid-connect
edited Nov 20 at 9:57
asked Nov 19 at 14:14
bomaboom
12812
12812
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53376514%2fasos-jwt-token-claims-are-not-visible-in-decoded-token-in-angular%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown