本文介绍了SCIM(跨域身份管理系统)核心支持的属性的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们正在为用户,组和几个自定义资源实现SCIM资源提供程序。
SCIM核心架构RFC 7643定义了用户资源,因此,仅 userName 和核心属性( id schemas )是必需的。加上它定义了 optional 属性,例如名称,profileUrl等。

We are implementing SCIM Resource Provider for Users, Groups and a couple of custom resources.SCIM Core Schema RFC 7643 defines User resource so, that only userName and core attributes (id, schemas) are required. Plus it defines optional attributes like name, profileUrl, etc.

某些 optional 属性对我们没有意义上下文(例如 ims ),或者不受支持,或者支持成本非常高。
另一方面,其他可选属性(例如 name )应为必需,并且应始终返回。

Some optional attributes do not make sense in our context (e.g. ims) or are not supported or very expensive to be supported.From the other hand, other optional attributes like name should be "required" and should be returned "always".

推荐这种表达方式是什么,以便客户知道应该提供哪些属性?
据我对rfc的了解,我们应该在/ Schemas端点上提供调整后的核心用户架构调整版本。这是正确的方法吗?
是否会使我们的提供程序不符合SCIM?

What is the recommended way to express this, so that the clients would know what attributes should be provided?As much I understand rfc, we should provide the adjusted, tweaked version of core User schema on /Schemas endpoint. Is it correct way?Would it make our Provider "none SCIM compliant"?

推荐答案

讨论已在scim邮件列表上开始。这是来自rfc的作者之一Phil Hunt的答案:

Discussion has been started on scim mailing list. Here is the answer from Phil Hunt, one of rfc authors:

IMO,您不必完全实现架构如在7643中发布。忽略属性是很常见的做法(例如,不关心ims的应用程序)。请注意,重命名标准属性或更改其格式会产生互操作性问题。

IMO, you do not have to implement the schema exactly as published in 7643. It is quite common practice to omit attributes (e.g. such as an app that doesn’t care about ims). Note that renaming standard attributes or changing their formats will produce interop concerns.

使用扩展机制定义您自己的应用特定属性(请参见7643的3.3和4.3的内容)。 EnterpriseUser示例)。

Use the extension mechanism to define your own app specific attributes (see section 3.3 of 7643 and 4.3 for the EnterpriseUser example).

您可以随意省略架构中未使用的属性。您可以在/ Schemas端点中记录服务器实际支持的内容。

You are free to omit unused attributes from your schema. You document what your server actually supports in the /Schemas endpoint.

完整的讨论可以在

这篇关于SCIM(跨域身份管理系统)核心支持的属性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-11 19:44