Question

我被告知我在这里描述的issue不是IdentityServer中的错误，所以我可能做错了什么：

此代码在QuickStart-project using EFCore中使用单个WSFederation实例作为身份提供程序。

注册提供者：

services.AddAuthentication()
            .AddWsFederation("WsFederation", options =>
            {
                options.SignInScheme = IdentityServerConstants.ExternalCookieAuthenticationScheme;
                options.Wtrealm = realm;
                options.MetadataAddress = metadata;
                options.Events.OnTicketReceived += OnTicketReceived;
            })

OnTicketReceived-事件处理程序：

/// <summary>
/// Transform the UPN-claim to the sub-claim to be compatible with IdentityServer4
/// </summary>
private async Task OnTicketReceived(TicketReceivedContext ticketReceivedContext)
{
     var identity = ticketReceivedContext.Principal.Identities.First();
     identity.AddClaim(new Claim("sub", ticketReceivedContext.Principal.FindFirstValue("http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier")));

}

当我添加第二个提供程序时，我将在尝试使用第二个提供程序时遇到异常，因为添加的第一个提供程序接收请求并在收到请求后立即抛出异常：

services.AddAuthentication()
.AddWsFederation("WsFederation_LocalHost", "WsFederation_LocalHost", options =>
                {
                    options.SignInScheme = IdentityServerConstants.ExternalCookieAuthenticationScheme;
                    options.Wtrealm = "urn:aspnetcorerp";
                    options.MetadataAddress = "http://localhost:5000/wsfederation";
                    options.Events.OnTicketReceived += OnTicketReceived;
                    options.RequireHttpsMetadata = false;
                })
                .AddWsFederation("WsFederation_SVN", "WsFederation_SVN", options =>
                {
                    options.SignInScheme = IdentityServerConstants.ExternalCookieAuthenticationScheme;
                    options.Wtrealm = realm;
                    options.MetadataAddress = metadata;
                    options.Events.OnTicketReceived += OnTicketReceived;
                    options.Events.OnSecurityTokenReceived += OnSecurityTokenReceived;
                })

我得到的例外是这个 - 如果我通过允许未经请求的登录来修复它，则会发生其他异常，因为它仍然会尝试使用错误的提供程序：

System.Exception：不允许未经请求的登录。在Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1.d__12.MoveNext（）

我发现它被提升的地方in IdentityServer4：

public async Task<bool> HandleRequestAsync()
    {
var result = await _inner.HandleRequestAsync();

如果我更改上面的代码以捕获异常，我可以解决这个问题，因为它会在之后传递正确的提供程序并且登录成功：

var result = false;
try
{
   result = await _inner.HandleRequestAsync();
}
catch (Exception) {}

我不满意必须分叉IdentityServer4来解决这个问题，所以我要求一个解决方案而不改变IdentityServer的代码。我可以介入并更改内容的地方是我的WSFederation端点的配置，在AccountController中右before starting the ExternalLogin或at the callback。

AccountController中的回调：

    [HttpGet]
    public async Task<IActionResult> ExternalLoginCallback()
    {
        // read external identity from the temporary cookie - I don't know how I could change which AuthenticationMiddleware gets called
        var result = await HttpContext.AuthenticateAsync(IdentityServer4.IdentityServerConstants.ExternalCookieAuthenticationScheme);

非常感谢任何我应该开始的提示。

Answer 1

知道了 - 解决方案是为不同的提供商设置不同的CallbackPath：

services.AddAuthentication()
                .AddWsFederation("WsFederation_LocalHost", "WsFederation_LocalHost", options =>
                {
                    options.SignInScheme = IdentityServerConstants.ExternalCookieAuthenticationScheme;
                    options.Wtrealm = "urn:aspnetcorerp";
                    options.MetadataAddress = "http://localhost:5000/wsfederation";
                    options.Events.OnTicketReceived += OnWsFedTicketReceived;
                    options.RequireHttpsMetadata = false;
                    options.CallbackPath = "/signin-wsfed-localhost";
                })
                .AddWsFederation("WsFederation_SVN", "WsFederation_SVN", options =>
                {
                    options.SignInScheme = IdentityServerConstants.ExternalCookieAuthenticationScheme;
                    options.Wtrealm = realm;
                    options.MetadataAddress = metadata;
                    options.Events.OnTicketReceived += OnWsFedTicketReceived;
                    options.CallbackPath = "/signin-wsfed-svn";
                })

IdentityServer4多个WSFederation-providers导致异常

1 个答案: