Identity and directory
The directory service is a component of Stacklok Enterprise. For a full comparison of ToolHive Community and Stacklok Enterprise capabilities, see Stacklok Enterprise.
The directory stores identities and group memberships used by the Connector Gateway and AI Gateway. Administrators manage these records through the console or API.
What it holds
| Record | Used for |
|---|---|
| Users | Resolve tokens and assign user budgets |
| Groups and subgroups | Grant connector access and assign group budgets |
| Identity providers | Broker OAuth from connectors to upstream services |
| Managed secrets | Store connector and identity provider credentials |
| Virtual API keys | Authenticate automated clients as a directory user |
How identity is resolved
The directory maps the issuer and subject in a caller's token to a user record. It returns the user's direct and inherited group memberships to the requesting component. Controls that require a directory identity deny callers without a matching record.
Connector access and budgets use directory groups. Cluster authorization policy uses OIDC claim groups. See Directory groups and OIDC claim groups.
Where you administer it
Use User management for users, groups, and subgroups. Use Identity providers and Managed secrets for connector authentication. Users manage their virtual keys under API keys in Your workspace.
The platform admin grant covers directory and budget administration. Use the
/v1 API for automation and bulk changes.
Contents
Users and groups
Create and administer directory users, groups, and subgroups, and understand how inherited membership affects connector access and budgets.
SCIM provisioning
Provision directory users and groups automatically from Okta, Entra ID, or any SCIM 2.0 identity provider.
Identity providers
Register the upstream identity providers that connectors authenticate against, and understand the read-only corporate provider entry.
Managed secrets
Store connector credentials encrypted at rest in the directory, and rotate the key that protects them.
Virtual API keys
Issue long-lived API keys that stand in for a user's own identity, so scripts and CI can reach the gateways without an interactive sign-in.