Introduction
CSI Auth is the shared identity platform for Jewelers Mutual applications. It covers how people and services prove who they are, what they are allowed to do, and how those decisions are audited. The platform is built on Auth0, with a thin internal layer on top so product teams work against one stable interface instead of against a vendor API directly.
These guides are written for engineers integrating an app with CSI Auth, and for teams migrating an app off a legacy authentication stack.
What CSI Auth provides
- A single sign-on experience across internal and customer-facing applications
- Central user, role, and permission management
- Enterprise, social, and database connections managed as code
- An audit trail of authentication and administrative events
Why Auth0
- Standards support: OIDC, OAuth 2.0, SAML
- Managed operations and availability
- Extensibility through Actions
- Terraform-managed configuration
What sits on top of Auth0
uia-auth-management-api: the internal proxy over the Auth0 Management API, with its own scope-based authorization- Terraform modules that own tenant configuration
- Shared Actions for token enrichment and login-time policy
Who this is for
- App engineers integrating login into a new or existing app
- Platform engineers managing clients, connections, and roles
- Teams migrating from a legacy authentication system
How to read these guides
Start with the Quickstart if you want something working today; it routes you to the implementation guide for your app type. Read Authentication first if you want the concepts before the code. Tenants and environments explains which environment your work belongs in.