Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

How to map Identity Server parameters in JwtBearerAuthenticationOptions ? #825

Closed
selganor74 opened this issue Nov 20, 2014 · 2 comments
Closed
Labels

Comments

@selganor74
Copy link

I'm trying to validate Jwt tokens released by Identity server on a Web API v2 app.

I'm actually using Katana's "UseJwtBearerAuthentication", but I have trouble in mapping Identity Server parameters in JwtBearerAuthenticationOptions.

I read the article http://leastprivilege.com/2013/09/15/using-authorizationserver-with-web-api-v2katanafirst-look/

where you show the "minimum" to have tokens decoded

app.UseJwtBearerAuthentication(new JwtBearerAuthenticationOptions
{
    AllowedAudiences = new[] { Constants.Audience },
    IssuerSecurityTokenProviders =
      new[] { new SymmetricKeyIssuerSecurityTokenProvider(
                Constants.AS.IssuerName,
                Constants.AS.SigningKey) }
});

Could you please explain how these parameters maps to IdentityServer configuration parameters ?

Thank you!

@brockallen
Copy link
Member

IIRC:
The audience is the "realm/scope name" from the RP config.
The signing key is the "Symmetric Signing Key" from the RP config.
The issuer name is the "Site ID" from IdSvr's global config.

@selganor74
Copy link
Author

YRC:
Thank you very much ! It worked perfectly.

Just to give all information: in my test set up the "Symmetric Signing Key" in the RP config is the same entered in Global "Key Configuration".

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants