Azure AD B2C破坏OIDC规格
我已经配置了一个自定义策略,AAD B2C ief per this 链接,现在试图将其集成到API网关中,为JWT授权者per this 链接。
但是,尝试配置授权者会引发错误
错误更新API网关V2授权器
BadRequestException
连接到 for Insuer https://tenant-domain.b2clogin.com/tenant-id-here/v2.0/ 。
请稍后再试。
错误:
无效的发行人:
。
发行人必须具有有效的发现端点,以'/.well-newone/openid-configuration结尾
实际发现端点为 https://tenant-domain.b2clogin.com/tenant-domain.onmicrosoft.com/b2c_1a_1a_signup_signup_signin/.well-well-.well-.well-.well-.well-.well-.well-.well-.well-.well-well-well-.well-.well-.well-.well-.well-.well-.well-.well-.well-.well-v.0/然而,已知/openid-configuration 返回下面的文档,其发行人与发现URL不同。
{
"issuer": "https://tenant-domain.b2clogin.com/tenant-id-here/v2.0/",
"authorization_endpoint": "https://tenant-domain.b2clogin.com/tenant-domain.onmicrosoft.com/b2c_1a_signup_signin/oauth2/v2.0/authorize",
"token_endpoint": "https://tenant-domain.b2clogin.com/tenant-domain.onmicrosoft.com/b2c_1a_signup_signin/oauth2/v2.0/token",
"end_session_endpoint": "https://tenant-domain.b2clogin.com/tenant-domain.onmicrosoft.com/b2c_1a_signup_signin/oauth2/v2.0/logout",
"jwks_uri": "https://tenant-domain.b2clogin.com/tenant-domain.onmicrosoft.com/b2c_1a_signup_signin/discovery/v2.0/keys",
"response_modes_supported": [
"query",
"fragment",
"form_post"
],
"response_types_supported": [
"code",
"code id_token",
"code token",
"code id_token token",
"id_token",
"id_token token",
"token",
"token id_token"
],
"scopes_supported": [
"openid"
],
"subject_types_supported": [
"pairwise"
],
"id_token_signing_alg_values_supported": [
"RS256"
],
"token_endpoint_auth_methods_supported": [
"client_secret_post",
"client_secret_basic"
],
"claims_supported": [
"name",
"given_name",
"family_name",
"email",
"sub",
"tid",
"iss",
"iat",
"exp",
"aud",
"acr",
"nonce",
"auth_time"
]
}
查看 this 问题,
有什么办法可以使它工作,还是我必须转到符合规格的OIDC提供商?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
请尝试配置发行人URL ,包括TFP ,以兼容。
有关更多详细信息,请参见: >令牌兼容性
说:
例如:
或
参考:
应用| Microsoft Doc
Please try to configure issuer URL including tfp for token compatibility.
For more details see: Token compatibility
which says:
For example:
or
References:
Apps | Microsoft Docs
rayterrill.com
除了 @kavyasaraboju-mt的答案之外,如果您使用的是自定义策略,则必须在
jwtissuer
中将IssuanceClaimpattern
设置为pertivere> epertionalwithtfp
per 。例如,在,添加元素
< item key =“ issuanceclaimpattern”> pertiatewithtfp</item gt;
代码>In addition to the answer by @kavyasaraboju-MT, if you're using custom policies, you must set the
IssuanceClaimPattern
toAuthorityWithTfp
in theJwtIssuer
Tehcnical Profile per these docs.e.g. using the LocalAccounts pack in active-directory-b2c-custom-policy-starterpack, add the element
<Item Key="IssuanceClaimPattern">AuthorityWithTfp</Item>
to the<Metadata>
element