IIS 10下的IdentityServer4 Windows登录无法成功进行身份验证

如何解决IIS 10下的IdentityServer4 Windows登录无法成功进行身份验证

使用本地计算机上的IIS Express,我可以运行IdentityServer4 QuickStart UI项目并成功登录。但是,一旦将其部署到生产环境中,我将无法使其正常工作。

在站点的“应用程序池”上,我有一个域帐户设置(几乎授予了所有可能的权限)。我尝试过切换“匿名身份验证”的各种方式。我已经以多种不同的方式(无SSL,仅SSL,完全开放的CORS,禁用了所有安全策略)从头开始重新创建了整个应用程序,甚至该应用程序的最基本版本似乎也遭受了完全一样的问题。

在对应用程序进行一些记录之后,我可以看到我正在从AD中获取主题ID和名称。

这里是ProcessWindowsLoginAsync方法,只有很少的日志记录更改。

private async Task<IActionResult> ProcessWindowsLoginAsync(string returnUrl)
{
    var result = await HttpContext.AuthenticateAsync(AccountOptions.WindowsAuthenticationSchemeName);
    if (result?.Principal is WindowsPrincipal wp)
    {
        var props = new AuthenticationProperties
        {
            RedirectUri = Url.Action("Callback"),Items =
            {
                { "returnUrl",returnUrl },{ "scheme",AccountOptions.WindowsAuthenticationSchemeName },}
        };

        var id = new ClaimsIdentity(AccountOptions.WindowsAuthenticationSchemeName);
        var sub = wp.FindFirst(ClaimTypes.PrimarySid).Value;
        id.AddClaim(new Claim(JwtClaimTypes.Subject,sub));
        id.AddClaim(new Claim(JwtClaimTypes.Name,wp.Identity.Name));
        
        _logger.LogInformation("Assigning claims. Subject {@Subject}. Name {@Name}",sub,wp.Identity.Name);

        if (AccountOptions.IncludeWindowsGroups)
        {
            var wi = wp.Identity as WindowsIdentity;
            var groups = wi!.Groups!.Translate(typeof(NTAccount));
            var roles = groups!.Select(x => new Claim(JwtClaimTypes.Role,x.Value));
            id.AddClaims(roles);
        }

        await HttpContext.SignInAsync(
            IdentityServerConstants.ExternalCookieAuthenticationScheme,new ClaimsPrincipal(id),props);
        return Redirect(props.RedirectUri);
    }

    return Challenge(AccountOptions.WindowsAuthenticationSchemeName);
}

上面的代码吐出类似的东西(去除了识别信息): Assigning claims. Subject S-0-0-00-0000000000-0000000000-0000000000-00000. Name DOMAIN\NAME

上面的代码执行后,将调用外部回调方法,并立即引发异常:

[HttpGet]
public async Task<IActionResult> Callback()
{
    var result = await HttpContext.AuthenticateAsync(IdentityServerConstants.ExternalCookieAuthenticationScheme);
    if (result?.Succeeded != true)
    {
        _logger.LogInformation("We were not successfully able to sign in. Failure: {@Failure}. None: {@None}",result?.Failure,result?.None);
        if (result?.Failure != null)
            throw result.Failure;
        throw new Exception("External authentication error");
    }

    if (_logger.IsEnabled(LogLevel.Debug))
    {
        var externalClaims = result.Principal.Claims.Select(c => $"{c.Type}: {c.Value}");
        _logger.LogDebug("External claims: {@claims}",externalClaims);
    }

    var (user,provider,providerUserId,claims) = FindUserFromExternalProvider(result);
    if (user == null)
        user = AutoProvisionUser(provider,claims);

    var additionalLocalClaims = new List<Claim>();
    var localSignInProps = new AuthenticationProperties();
    ProcessLoginCallbackForOidc(result,additionalLocalClaims,localSignInProps);

    var issuer = new IdentityServerUser(user.SubjectId)
    {
        DisplayName = user.Username,IdentityProvider = provider,AdditionalClaims = additionalLocalClaims
    };

    await HttpContext.SignInAsync(issuer,localSignInProps);
    await HttpContext.SignOutAsync(IdentityServerConstants.ExternalCookieAuthenticationScheme);

    var returnUrl = result.Properties.Items["returnUrl"] ?? "~/";
    var context = await _interaction.GetAuthorizationContextAsync(returnUrl);
    
    await _events.RaiseAsync(new UserLoginSuccessEvent(provider,user.SubjectId,user.Username,true,context?.ClientId));

    if (context != null)
        if (await _clientStore.IsPkceClientAsync(context.ClientId))
            return this.LoadingPage("Redirect",returnUrl);

    return Redirect(returnUrl);
}

从日志中,我可以知道它在尝试进行身份验证后立即失败。没有其他错误,但是有一些有趣的记录日志(按顺序):

Performing protect operation to key {xxxxxxxx-xxxx-xxxx-xxxx-b7e4d6dd250a} with purposes ('C:\websites\identity.ourdomain.com','Microsoft.AspNetCore.Authentication.Cookies.CookieAuthenticationMiddleware','idsrv.external','v2').

AuthenticationScheme: idsrv.external signed in.

Executing RedirectResult,redirecting to /External/Callback

Executing action method IdentityServer4.Quickstart.UI.ExternalController.Callback (Idsvr.Api) - Validation state: Valid

AuthenticationScheme: idsrv.external was not authenticated.

(Exception)

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-