Voyti

Voyti

User management, authentication & authorization

SCIM Provisioning

SCIM 2.0 provisioning for identity providers. The voyti-api-scim package exposes Voyti users through the SCIM Users resource and Voyti RBAC roles through the SCIM Groups resource.

Create an issue

The Users resource represents existing Voyti users. userName, emails, and active are returned attributes; password is accepted as a write-only provisioning attribute. The Groups resource represents Voyti RBAC roles: displayName is the role name and members are user assignments. All routes use the base API’s Bearer-token authentication and administrator-access policy.

Route nameMethodPathPurpose
voyti/api-scim-v2-service-provider-configGETv2/ServiceProviderConfigSCIM service provider capabilities
voyti/api-scim-v2-resource-typesGETv2/ResourceTypesList supported resource types
voyti/api-scim-v2-schemasGETv2/SchemasList supported schemas
voyti/api-scim-v2-schemaGETv2/Schemas/{schema}View a schema
voyti/api-scim-v2-bulkPOSTv2/BulkProcess sequential User and Group operations
voyti/api-scim-v2-users-indexGETv2/UsersList Voyti users
voyti/api-scim-v2-users-createPOSTv2/UsersCreate a Voyti user
voyti/api-scim-v2-users-searchPOSTv2/Users/.searchSearch Voyti users
voyti/api-scim-v2-users-viewGETv2/Users/{id}View a Voyti user
voyti/api-scim-v2-users-replacePUTv2/Users/{id}Replace a Voyti user
voyti/api-scim-v2-users-patchPATCHv2/Users/{id}Patch a Voyti user
voyti/api-scim-v2-users-deleteDELETEv2/Users/{id}Delete a Voyti user
voyti/api-scim-v2-groups-indexGETv2/GroupsList RBAC roles
voyti/api-scim-v2-groups-createPOSTv2/GroupsCreate an RBAC role
voyti/api-scim-v2-groups-searchPOSTv2/Groups/.searchSearch RBAC roles
voyti/api-scim-v2-groups-viewGETv2/Groups/{id}View an RBAC role
voyti/api-scim-v2-groups-replacePUTv2/Groups/{id}Replace an RBAC role
voyti/api-scim-v2-groups-patchPATCHv2/Groups/{id}Patch an RBAC role
voyti/api-scim-v2-groups-deleteDELETEv2/Groups/{id}Delete an RBAC role

Collection endpoints support SCIM pagination, attribute selection, filtering, and sorting. User and Group resources support replacement with PUT, partial updates with PATCH, and standard SCIM error responses.

User and Group responses include opaque ETag values. PUT, PATCH, and DELETE honor If-Match; a stale conditional write returns 412 with SCIM invalidVers. If-None-Match can be used for conditional reads.

POST /v2/Bulk processes sequential User and Group operations and returns a per-operation status and response. Bulk requests require the SCIM BulkRequest schema, support up to 100 operations, and are limited to a 1 MiB payload. Discovery endpoints describe the provider, resource types, and schemas. Search requests can use either GET query parameters or the resource-specific POST /v2/Users/.search and POST /v2/Groups/.search endpoints.

Voyti provides a focused SCIM 2.0 service-provider profile for identity lifecycle management and RBAC role membership. It covers the operations needed to provision Voyti accounts and roles without claiming to model every possible SCIM resource, extension, or attribute.

AreaImplementation status
ResourcesVoyti users and RBAC roles, exposed as SCIM Users and Groups
DiscoveryService provider configuration, resource types, and supported schemas
Lifecycle operationsCreate, read, replace, partial update, and delete
Query operationsPagination, attribute selection, supported filters, and sorting
Bulk operationsSequential User and Group operations, limited to 100 operations, with bulkId references and failOnErrors
Conditional requestsETag, If-Match, and If-None-Match
Resource scopeuserName, emails, active, and write-only password for users; displayName and members for groups
SearchGET query parameters and POST /v2/Users/.search or POST /v2/Groups/.search are supported
PATCHadd, remove, and replace are supported for the mapped attributes, with the required PatchOp schema URI enforced
Resource metadataLocation and meta.location are emitted for resource responses
Extensions and additional resourcesNot included in this focused profile

SCIM requests should be sent over HTTPS. The package supplies Bearer-token authentication and administrator-access enforcement through voyti-api; the application remains responsible for TLS configuration and deployment-level security.