Content
View differences
Updated by Dominic Bräunlein about 1 year ago
**As** a SCIM client
**I want to** update OpenProject with user changes
**so that** OpenProject has their users stay in sync with the Identity Provider (IdP) idP
**Acceptance criteria**
* Implement CRUD API endpoints are implemented according to SCIM specifications. specification..
* User The changes are processed should be done by a system-level system user (pending clarification if a dedicated "SCIM User" is needed). (needs clarification)
* <br>
<br>
**Technical notes**
* Prefer utilizing Best would be to use an existing SCIM Ruby gem to streamline development and ensure specification compliance.
<br>
**Open Questions**
* Should it be the System user or a specific other user like "SCIM user"?
**Permissions and visibility considerations**
* API access is restricted to administrators. Admins only
* Available only Only when the Enterprise plan with plan: Corporate is active.
<br>
**Out of scope**
* Advanced attribute synchronization beyond basic CRUD operations.
* Token expiration and advanced scope management.
<br>
**I want to** update OpenProject with user changes
**so that** OpenProject
**Acceptance criteria**
* Implement CRUD API endpoints
* User
* <br>
<br>
**Technical notes**
* Prefer utilizing
<br>
* Should it be the System user or a specific other user like "SCIM user"?
* API access is restricted to administrators.
* Available only
<br>
**Out of scope**
* Advanced attribute synchronization beyond basic CRUD operations.
* Token expiration and advanced scope management.
<br>