Store app data keyed to each account
Connect
SPIRITT
KeycloakKeycloak
Sign-in your apps own
SPIRITT provisions a dedicated Keycloak realm for your organization and wires it into the apps it builds. It registers each app's client and redirect URIs, implements login and sessions, and tests the full sign-in flow before launch.
What you can do with Keycloak.
One account across your apps
A shared organization realm lets customers use one account for every app you ship, with separate realms when a product needs isolated users.
Clients configured right
Every app gets its own client and redirect URIs, so login boundaries stay explicit and easy to debug.
SPIRITT accounts welcome
Apps can also let people sign in with their existing SPIRITT account through a dedicated per-app client.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the apps that need their own users and sign-in.
02
Turn on app sign-in
Enable the built-in Keycloak integration. SPIRITT creates your organization's realm along with its administrator access.
03
Delegate an outcome
Ask SPIRITT to add sign-in to an app or launch a new member portal, tested end to end on the live URL.
Hand over a mission.
Choose a mission. Make it yours.
Put Keycloak to work.
Give every app a front door
Questions
Keycloak, with SPIRITT.
01What does the Keycloak integration give me?+
A dedicated Keycloak realm for your organization's apps, created by SPIRITT along with realm administrator access. SPIRITT then registers a client for each app, sets its redirect URIs and builds the login flow into the app.
02Do I need it to keep a dashboard private?+
No. Apps that only need to be visible to members of your organization are already protected by SPIRITT's private access. Use Keycloak when an app needs its own users, accounts and sign-in experience, such as a customer portal or member area.
03Can several apps share one login?+
Yes. One organization realm serves every app you register as a client, so customers can use a single account across products. Each app keeps its own client and redirect URIs, and a separate realm is available when a product needs isolated users.
04Can people sign in with their SPIRITT account?+
Yes. For apps meant for SPIRITT users, SPIRITT creates a dedicated sign-in client per app, with its callback on that app's own address.
05How are realm admin credentials protected?+
Apps receive only the realm and discovery details they need to sign users in. Realm administrator credentials stay in your workspace vault for administration. At organization scope every workspace in the organization can administer the realm; workspace scope keeps it to one.
06What happens if sign-in breaks?+
SPIRITT checks the client's redirect URIs and the app's sign-in settings against the deployed address, fixes the mismatch and retests the flow. Re-running setup repairs the same realm and keeps its existing credentials.