Add FAQ to SCIM integration doc (#18664)
Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>
Juan Cañete committed
Oct 3, 2024 at 14:34 UTC
64d33e6edac0cf730d68494b4fc02b3b123676c2
1 file changed
+14
integrations/cloud-authentication/metadata.yaml
+14
@@ -169,5 +169,19 @@
169
The externalID in SCIM must correspond to the subfield in OIDC. Any deviation from this mapping may result
170
in incorrect user identification and authentication failures.
171
172
+ ## FAQ
173
+
174
+ ### Why aren’t users automatically added to Netdata spaces when they’re created through SCIM?
175
+
176
+ Currently, our SCIM server supports only the User resource. We plan to add support for the Group resource in the future.
177
+
178
+ In a Netdata space, users can belong to multiple rooms and have different roles (e.g., admin, manager). Additionally, the same organization may have multiple spaces.
179
+
180
+ As we don't yet support groups, when a user is created through SCIM, we don’t have a way to determine which spaces, rooms, and roles the user should be assigned to.
181
+
182
+ Once we implement support for the Group resource, admins will be able to map SCIM groups to Netdata memberships, so this assignment will be done automatically.
183
+
184
+ Until then, SCIM can only be used to grant or block access to Netdata for users in your organization. After a user is created, it is up to the Netdata administrator to manually invite them to spaces, rooms and assign roles.
185
+
186
### Reference
187
[SCIM Specification](https://scim.org)