AutoRFP supports SCIM 2.0 (RFC 7643/7644) for automated user provisioning and deprovisioning.
Authentication
SCIM requests are authenticated via OAuth 2.0 Bearer Tokens (RFC 6750).
Supported Endpoints
User Operations
Endpoint | Methods | Description |
| GET, POST | List users (with filtering/pagination) or create a new user |
| GET, PUT, PATCH, DELETE | Retrieve, replace, update, or deactivate a specific user |
Discovery
Endpoint | Method | Description |
| GET | SCIM provider capabilities |
| GET | Supported resource types |
| GET | All supported schemas |
| GET | A specific schema definition |
User Schema
SCIM Attribute | Required | Notes |
| Yes | Must be a valid email address. Used as the primary user identifier. |
| Yes | First name |
| Yes | Last name |
| Read-only | Auto-generated from given/family name |
| Yes | Controls whether the user can access the account |
| No | Job title |
| No | External identifier from your IdP |
Filtering & Pagination
Filtering
The GET /Users endpoint supports SCIM filtering via the filter query parameter.
Filterable attributes: userName, name.givenName, name.familyName, displayName, active, title, externalId, id
Supported operators: eq, ne, co, sw, ew, gt, ge, lt, le, pr
Logical operators: and, or, not
Examples:
filter=userName eq "[email protected]"
filter=active eq true and name.givenName sw "John"
Pagination
Parameter | Default | Max |
| 1 | — |
| 100 | 1000 |
Deprovisioning Behaviour
When a user is deactivated via DELETE or by setting active to false, the user is soft-deleted. Their access is revoked immediately but their record is retained for audit purposes.
Current Limitations
Groups - Group resources are not currently supported. User provisioning and deprovisioning is managed at the individual user level.
Roles - Role assignment via SCIM is not currently supported. Roles are managed within the application.