gpt4 book ai didi

adfs2.0 - 使用 ADFS 2.0 实现 SSO 时获取 NameIDPolicyError

转载 作者:行者123 更新时间:2023-12-04 02:57:07 25 4
gpt4 key购买 nike

我正在尝试使用 SSO 将第三方系统与 ADFS 2.0 连接起来。我创建了依赖方信任和两个声明规则

规则#1

c:[Type == "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"]
=> issue(Type = "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier", Issuer = c.Issuer, OriginalIssuer = c.OriginalIssuer, Value = c.Value, ValueType = c.ValueType, Properties["http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/format"] = "urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress");

规则 #2

c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname", Issuer == "AD AUTHORITY"]
=> issue(store = "Active Directory", types = ("http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"), query = ";mail;{0}", param = c.Value);

我可以访问 ADFS 服务器但出现此错误

MSIS1000: The SAML request contained a NameIDPolicy that was not satisfied by the issued token. Requested NameIDPolicy: AllowCreate: False Format: urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress SPNameQualifier: https://xxx.xxx.com/sso. Actual NameID properties: null. 

有什么想法吗?

最佳答案

这一段是线索:

SPNameQualifier: https://xxx.xxx.com/sso. Actual NameID properties: null.

因此 SP 的 NameID(实体 ID)为“https://xxx.xxx.com/sso”,但在 ADFS 端没有配置这样的名称。

您需要使用 Properties [] 构造将其添加到声明中。

引用:ADFS – SAML 2.0 Identity Provider and SaaS Service Providers .

关于adfs2.0 - 使用 ADFS 2.0 实现 SSO 时获取 NameIDPolicyError,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/16403359/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com