Zitadel (OIDC)
Zitadel
People sign in through Zitadel, the identity provider shared across the Fleetworks suite.
The web app runs the OIDC authorization code flow with PKCE as a public client, with no client secret. The API verifies each token against the issuer’s published keys.
Chorus never sees a password. On first sign-in it creates a user from the identity provider’s subject; roles live in Chorus, not in Zitadel.
More integrations
All integrations →- 01
Your HTTPS endpoints
Any service that can receive an HTTPS POST and check an HMAC signature can follow changes in Chorus.
- 02
Expo push notifications
When a webhook delivery is dead-lettered, Chorus sends a push through Expo to the organization’s registered devices.
- 03
Yellow Pages
A record may point at a YellowPages service by id, so you can tell which service a record belongs to.