前言
在 ASP.NET Core 中,我们常使用基于 JWT 的认证:
services.AddAuthentication(option =>
{
option.DefaultAuthenticateScheme = JwtBearerDefaults.AuthenticationScheme;
option.DefaultChallengeScheme = JwtBearerDefaults.AuthenticationScheme;
}).AddJwtBearer(options =>
{
options.TokenValidationParameters = new TokenValidationParameters
{
ValidateIssuer = true,
ValidateAudience = true,
ValidateLifetime = false,
ValidateIssuerSigningKey = true,
ValidIssuer = Configuration["JwtToken:Issuer"],
ValidAudience = Configuration["JwtToken:Issuer"],
IssuerSigningKey = new SymmetricSecurityKey(Encoding.UTF8.GetBytes(Configuration["JwtToken:SecretKey"]))
};
});
但有时候,我们需要使用自定义认证,比如使用QueryString(htttp://xxx?_key=xxx),只要请求中包含的_key
的值正确即可。
为了实现自定义认证,我们决定仿照AddJwtBearer
的实现机制。
AddJwtBearer
实际执行的是AddScheme
方法:
public static AuthenticationBuilder AddJwtBearer(this AuthenticationBuilder builder, string authenticationScheme, string? displayName, Action configureOptions)
{
builder.Services.TryAddEnumerable(ServiceDescriptor.Singleton());
return builder.AddScheme(authenticationScheme, displayName, configureOptions);
}
JwtBearerHandler
是具体的处理程序,继承自AuthenticationHandler
,主要代码在HandleAuthenticateAsync
内:
protected override async Task HandleAuthenticateAsync()
{
...
if (string.IsNullOrEmpty(token))
{
string authorization = Request.Headers.Authorization.ToString();
// If no authorization header found, nothing to process further
if (string.IsNullOrEmpty(authorization))
{
return AuthenticateResult.NoResult();
}
if (authorization.StartsWith("Bearer ", StringComparison.OrdinalIgnoreCase))
{
token = authorization.Substring("Bearer ".Length).Trim();
}
// If no token found, no further work possible
if (string.IsNullOrEmpty(token))
{
return AuthenticateResult.NoResult();
}
}
...
foreach (var validator in Options.SecurityTokenValidators)
{
if (validator.CanReadToken(token))
{
...
var tokenValidatedContext = new TokenValidatedContext(Context, Scheme, Options)
{
Principal = principal,
SecurityToken = validatedToken
};
...
tokenValidatedContext.Success();
return tokenValidatedContext.Result!;
}
}
...
}
从Request.Headers.Authorization
获取token,然后用Options.SecurityTokenValidators
验证token合法后,返回结果。
创建DemoAuthenticationOptions
,继承自AuthenticationSchemeOptions
:
public class DemoAuthenticationOptions : AuthenticationSchemeOptions
{
public const string Scheme = "Demo";
}
DemoAuthenticationHandler
创建DemoAuthenticationHandler
,继承自AuthenticationHandler
:
public class DemoAuthenticationHandler : AuthenticationHandler
{
public DemoAuthenticationHandler(IOptionsMonitor options, ILoggerFactory logger, UrlEncoder encoder, ISystemClock clock)
: base(options, logger, encoder, clock)
{ }
protected override async Task HandleAuthenticateAsync()
{
throw new NotImplementedException();
}
}
实现 HandleAuthenticateAsync 方法
从请求的Query
中获取key
,然后检查是否合法:
protected async override Task HandleAuthenticateAsync()
{
if (!Request.Query.TryGetValue("_key", out var keys))
{
return AuthenticateResult.NoResult();
}
var key = keys.FirstOrDefault();
//到数据库检索
if (key =="123456")
{
var claims = new List
{
new Claim(ClaimTypes.Name, "My IO")
};
var identity = new ClaimsIdentity(claims, DemoAuthenticationOptions.Scheme);
var identities = new List { identity };
var principal = new ClaimsPrincipal(identities);
var ticket = new AuthenticationTicket(principal, DemoAuthenticationOptions.Scheme);
return AuthenticateResult.Success(ticket);
}
return AuthenticateResult.NoResult();
}
定义扩展方法
定义扩展方法,使用我们上面创建的DemoAuthenticationHandler
:
public static class AuthenticationBuilderExtensions
{
public static AuthenticationBuilder AddDemoAuthentication(this AuthenticationBuilder authenticationBuilder, Action options)
{
return authenticationBuilder.AddScheme(DemoAuthenticationOptions.Scheme, options);
}
}
使用
修改Startup.cs:
services.AddAuthentication(option =>
{
option.DefaultAuthenticateScheme = DemoAuthenticationOptions.Scheme;
option.DefaultChallengeScheme = DemoAuthenticationOptions.Scheme;
})
.AddDemoAuthentication(options => { });
结论
当不加Query
或使用错误的key
时,返回401 认证失败:
仅当使用正确的key
时,API 访问成功: