2.5. RH-SSO 7.3
以下变化已从 RH-SSO 7.2 变为 RH-SSO 7.3。
2.5.1. 授权服务的更改 复制链接链接已复制到粘贴板!
复制链接链接已复制到粘贴板!
添加了对 UMA 2.0 的支持。这个 UMA 规范版本引进了一些有关从服务器获取权限的方式的重要变化。
以下是 UMA 2.0 支持的主要变化。详情请查看授权服务指南。
- 已删除授权 API
- 在 UMA 2.0 (UMA 1.0)之前,客户端应用程序使用授权 API 从服务器获取权限,格式为 RPT。UMA 规范的新版本删除了授权 API,它也已从 Red Hat Single Sign-On 中删除。在 UMA 2.0 中,RPTs 现在可以使用特定的授权类型从令牌端点获取。详情请查看授权服务指南。
- 已删除权利 API
- 随着 UMA 2.0 的推出,我们决定利用令牌端点和 UMA 授权类型从 Red Hat Single Sign-On 获取 RPT,并避免有不同的 API。Entitlement API 提供的功能相同,仍然可以获得一组一个或多个资源和范围的权限(如果没有提供资源或范围)。详情请查看授权服务指南。
- 对 UMA Discovery 端点的更改
- UMA Discovery 文档已更改 ,请参阅授权服务指南。
- 对 Red Hat Single Sign-On Authorization JavaScript 适配器的更改
Red Hat Single Sign-On Authorization JavaScript 适配器(keycloak-authz.js)已更改,以满足 UMA 2.0 引入的更改,同时保持与之前相同的行为。主要变化是如何调用
授权和
权利
方法,它们现在预期是表示授权请求的特定对象类型。这个新对象类型通过支持 UMA grant 类型支持的不同参数,提供了从服务器获取权限的更大的灵活性。详情请查看授权服务指南。One of the main changes introduced by this release is that you are no longer required to exchange access tokens with RPTs in order to access resources protected by a resource server (when not using UMA). Depending on how the policy enforcer is configured on the resource server side, you can just send regular access tokens as a bearer token and permissions will still be enforced.
One of the main changes introduced by this release is that you are no longer required to exchange access tokens with RPTs in order to access resources protected by a resource server (when not using UMA). Depending on how the policy enforcer is configured on the resource server side, you can just send regular access tokens as a bearer token and permissions will still be enforced.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Red Hat Single Sign-On Authorization Client Java API 的更改
-
当升级到 Red Hat Single Sign-On Authorization Client Java API 的新版本时,您会注意到一些表示类被移到
org.keycloak:keycloak-core
中。