1Password SCIM Bridge has endpoints for specific functionality. They aren’t used by identity providers for integrations. Unless otherwise indicated, endpoints are authenticated using the bearer token paired with the associated scimsession file that was used to deploy your SCIM bridge.
SCIM bridge endpoints
| Endpoint | Description |
|---|---|
/ | Redirects to /app. |
/app | The SCIM bridge status page, which displays health status and allows you to download logs. Requires a bearer token for authentication. |
/health | If health monitoring is turned on, this endpoint is used for health checks. A GET request, authenticated with the SCIM bridge bearer token, will return an HTTP status code with the health of components in JSON format. |
/monitoring | If health monitoring is turned on, this endpoint is used by Checkly which authenticates with its own bearer token. |
/ping | For checking whether the SCIM bridge is available. Unauthenticated. |
/metrics | Used for metrics with Prometheus. |
SCIM protocol endpoints
/scim/Users/scim/Groups/scim/Schemas/scim/ResourceTypes/scim/Schemas/scim/ServiceProviderConfig
Learn more about these endpoints in SCIM RFC 7644 section 3.2.
Learn more
Was this article helpful?
Glad to hear it! If you have anything you'd like to add, feel free to contact us.
Sorry to hear that. Please contact us if you'd like to provide more details.