Closed mokeyish closed 7 years ago
ASP.NET Core 2.0 has landed, as of about an hour ago. Does this call for a bump to 2.0 (alongside IdentityModel.AspNetCore.OAuth2Introspection & others) and keep a 1.x branch around for maintenance?
Would you like any help or are you ticking along just fine?
Some handy references:
Microsoft.AspNetCore.Authentication.JwtBearer 2.0 (this is good as an implementation reference, most importantly the new configuration scheme through services and the IAuthenticationHandler
implementation.)
Yup, getting errors when trying to app.UseIdentityServerAuthentication(...
Thank you,I have found solution for this problem。
@mokeyish what is the solution?
@kspearrin
services.AddJwtBearerAuthentication(options => { options.Authority = http://xxx; options.RequireHttpsMetadata = false; options.Audience = "api1"; }); app.UseAuthentication();
So we no longer use this library?
Well, Jetbearer is only half the functionality. It can't dereference access tokens that aren't plain JWTs.
On 16 Aug 2017, at 10:47 am, Kyle Spearrin notifications@github.com wrote:
So we no longer use this library?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
@kspearrin Yes,we no longer use this library,Asp.Net Core 2.0 has already wrapped up authentication functionality.Asp.Net core 2.0 recognize different authentication by token_type.
This sounds like this issue is still valid when using reference tokens?
You could move it to OAuth2Introspection?
On 16 Aug 2017, at 11:48 pm, urbanhusky notifications@github.com wrote:
This sounds like this issue is still valid when using reference tokens?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
or the other way round rather.