设置设置的任何更新都会弄乱承载令牌 [英] Any update to provisioning settings messes up bearer token

查看:66
本文介绍了设置设置的任何更新都会弄乱承载令牌的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在非画廊应用程序"供应选项卡中,更改任何供应设置也会更改秘密令牌",因此在保存"之后,大多数供应命令都会失败,并出现未授权"错误.

In the Non-gallery application provisioning tab, changing any provisioning setting also changes the Secret Token, so that after the Save, most of the provisioning commands fail with an Unauthorized error.

这在Provisioning刀片中并不明显,因此,用户每次更新任何内容时都会失去一个供应周期.

This is not evident in the Provisioning blade, so the user winds up loosing a provisioning cycle every time anything gets updated.

推荐答案

请注意,如果SCIM终结点需要来自Azure AD以外的发行者的OAuth承载令牌,则将所需的OAuth承载令牌复制到可选的Secret Token字段中.如果将此字段留空,则Azure AD包含OAuth承载令牌 从Azure AD发出的每个请求.使用Azure AD作为身份提供者的应用程序可以验证此Azure AD颁发的令牌.

Please note that if the SCIM endpoint requires an OAuth bearer token from an issuer other than Azure AD, then copy the required OAuth bearer token into the optional Secret Token field. If this field is left blank, then Azure AD included an OAuth bearer token issued from Azure AD with each request. Apps that use Azure AD as an identity provider can validate this Azure AD -issued token.

当我进行更改并保存时,机密值没有得到更新.但是,如果为空,则

As I do changes and save it, the secret value is not getting updated. However, if it is blank Azure AD includes an OAuth bearer token issued from Azure AD with each request.


这篇关于设置设置的任何更新都会弄乱承载令牌的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆