Fits the estate you already have
Enterprise deals are rarely lost on features. They are lost because the buyer's HR platform cannot provision users, or a critical application only speaks SAML. BlackWall meets those systems where they are — without asking your users to authenticate twice.
SAML 2.0 identity provider
Many enterprise applications cannot speak OIDC and never will. BlackWall acts as a SAML 2.0 IdP for them, reusing the same WebAuthn portal login — so users never meet a second authentication surface.
SCIM 2.0 provisioning
Workday, Okta, Entra ID, Google Workspace, BambooHR and Rippling push user-lifecycle changes straight into BlackWall. A leaver in HR becomes a deprovisioned user here, with no operator retyping anything.
Signed webhooks
Every project-scoped audit event can be fanned out to your own systems, HMAC-signed and delivered in the background so the originating request never waits on your endpoint.
One login, many protocols
The point of federation is that the user should not care which protocol an application chose. Whichever door they arrive at, the proof of identity is the same WebAuthn assertion.
- Per-project service provider registry — each project keeps its own list of registered SAML applications.
- Standard bindings — HTTP-Redirect and HTTP-POST for requests, HTTP-POST for responses.
- Metadata endpoint — hand the downstream application one URL and let it configure itself.
- No second password — SAML sign-on reuses the portal's passwordless login rather than introducing a fallback credential.
- Project-scoped provisioning — every SCIM operation targets one project, so users land in the right place with the right assignment.
Events your systems can trust
A webhook that cannot be verified is a liability. BlackWall signs every delivery so your receiver can prove the payload came from your identity provider and has not been replayed.
- HMAC-SHA256 signature — a timestamped signature header your receiver recomputes over the raw body.
- Stable event identity — an event ID that stays constant across retries, so idempotent handling is straightforward.
- Versioned envelope — a declared payload version, so your receivers are not broken by a future change.
- Non-blocking dispatch — deliveries run in the background; a slow endpoint never slows a user's login.