Skip to content
This repository was archived by the owner on Dec 13, 2018. It is now read-only.

Conversation

@pblxptr
Copy link

@pblxptr pblxptr commented Jul 13, 2018

With the code below, JwtBearer does not automaticly call authority service in order to obtain authentication / authorization manifest eg. public key, and does not occur any errors like "unable to retrive document".

//ConfigureServices
services.AddAuthentication(JwtBearerDefaults.AuthenticationScheme) .AddJwtBearer(options => { options.Authority = "http://localhost:5050"; options.Audience = "{yourAudience}"; });

//Configure
app.UseAuthentication

HaoK and others added 28 commits July 20, 2017 21:18
Changes: - Remove floating versions - Disable myget feeds during a Universe build - Use package-specific MSBuild variables. Pattern = `packageId.Pascalize() + "PackageVersion"`, with a few exceptions.
@dnfclas
Copy link

dnfclas commented Jul 13, 2018

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

❌ bielu000 sign now
You have signed the CLA already but the status is still pending? Let us recheck it.

@pblxptr pblxptr changed the title Release/2.0 Auth policy does not call authority server in order to obtain auth manifest Jul 13, 2018
@Tratcher
Copy link
Member

I don't think you intended this to be a pull request as it does not contain any new commits. Please open an issue at https://github.com/aspnet/Security/issues with more details about your scenario.

@Tratcher Tratcher closed this Jul 13, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

8 participants