Skip to content
This repository has been archived by the owner on Jul 4, 2020. It is now read-only.

Technical name for groups #130

Closed
sschum opened this issue Aug 3, 2015 · 3 comments
Closed

Technical name for groups #130

sschum opened this issue Aug 3, 2015 · 3 comments
Assignees
Labels

Comments

@sschum
Copy link

sschum commented Aug 3, 2015

At the moment the scim_group stores only "displayName". In our project we have a need for a technical name. So is it possible to add a new (optional) property "name" for each scim_group?

@tkrille
Copy link
Member

tkrille commented Aug 3, 2015

Hi @sschum,

this is not part of the SCIM 2 API. But SCIM provides extension points either by using "extensions" or custom resource types. Custom resource types have to be implemented in OSIAM, but are globally available then. As not everybody needs your feature, I would refrain from implementing it this way. Using extensions might be the best option for you, but unfortunately OSIAM does not support extensions for groups, yet. So if you need this feature, please create another issue for that.

But, why exactly do you need this? Groups support (like any resource) the external_id field. That should be the only thing needed, if you want to identify a group without using the UUID, i.e. give it a human-readable but computer-parseable name.

@tkrille tkrille self-assigned this Aug 3, 2015
@sschum
Copy link
Author

sschum commented Aug 3, 2015

I think the idea with the extensions for groups is better than only one additional field. For us this feature is also useful.

I thought about the externalId. And i think this is also a way for us. but the extensions are more beautiful.

We would prefer the solution with the extensions and I will open up a new issue in github.

@tkrille
Copy link
Member

tkrille commented Aug 3, 2015

Question has been answered -> closing issue.

@tkrille tkrille closed this as completed Aug 3, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants