Identity APIs
you will not fight.
OAuth 2, OIDC, SAML, JWT, SCIM, and a clean REST surface — same shape self-hosted or cloud. Standards first. No SDK gymnastics.
- OAuth 2 / OIDC / SAML 2 / JWT
- OpenAPI 3 REST surface
- Custom REST connector
A developer's week with Monofor.
Less time arguing with auth, more time shipping product. Identity becomes a backend you can script against.
Add SSO to the new internal tool
You pick OIDC, register a Monosign client, drop the discovery URL into your framework, and the redirect dance just works. Five-minute setup, no SDK to learn.
Wire identity-as-code into CI
You script user and group provisioning through the REST API, pin it to idempotency keys, and run it in your pipeline. Every environment ships with the right access by default.
Hook the audit stream into the SIEM
A webhook subscription picks up identity events; you sign-verify them and ship them straight into your SIEM. No batch jobs, no polling.
What developers get with Monofor.
Four properties that make Monofor feel like a service, not a vendor: standards, REST, custom-app friendliness, and deployment parity.
Standards first, no proprietary tokens
OAuth 2, OpenID Connect, SAML 2, JWT, SCIM — the protocols you already know. Drop Monofor in and keep your auth code portable.
- OAuth 2 authorization-code, PKCE, client-credentials
- OpenID Connect with discovery and JWKS
- SAML 2 with ADFS-compatible assertions
- JWT issuance and validation
A REST API you can actually script against
Users, groups, entitlements, devices, audits — all reachable through a clean REST surface. OpenAPI spec, cursor pagination, idempotency keys.
- OpenAPI 3 spec, downloadable
- Idempotency keys for safe retries
- Cursor-based pagination, predictable filters
- Webhook events on identity change
Custom apps connect in an afternoon
Got an in-house app the catalog does not cover? The custom REST integration turns any HTTP-speaking app into an SSO target.
- Custom REST application connector
- Custom OIDC application support
- Browser-extension fallback for legacy apps
- API-based sign-in for service accounts
Same shape, self-hosted or cloud
Develop against a local Monosign tenant, ship to your own VPC, or run as a managed cloud tenant — same endpoints, same shape, same auth.
- Docker, Helm, and bare-metal deployment
- Kubernetes-native Monopam operator
- Sandbox tenants for CI
- Configuration-as-code patterns
Straight into the docs.
Deep-links into the help articles that engineers actually paste into PRs.
Standards & protocols
APIs & automation
Custom apps
Ready to start managing
identities the right way?
Spin up a fully-loaded trial tenant in under five minutes. No credit card. No sales gate.