Component
core/security/supertokens
An authentication core: the backend service that holds an application's users, their credentials and their sessions, and issues and verifies the tokens that carry a session between requests. It is reached only by an application's own backend, over HTTP, through one of the project's backend client libraries configured with this component's published endpoint. Wire here when sign-in belongs to the application: the application's backend owns the sign-in routes and the screens a user sees, and this component sits behind it as the place the user records live. Wire `core/security/keycloak` instead when sign-in belongs to the platform, as an identity provider applications reach over OpenID Connect and SAML. The core keeps no durable state of its own: it needs a PostgreSQL backend on its required `backend` socket, where it creates and migrates its own tables at startup, and with none wired the build halts. It answers administrative calls over the whole user store to anything that can reach it and issues no API key by default, so it is published on an in-cluster address only; attaching a key to the `api_key` slot requires one. Realized on Kubernetes via its Helm Recipe, which synthesizes the core as a stateless Deployment behind a ClusterIP Service on its HTTP port. Exports its host, port, endpoint and protocol to consumers, where the endpoint is the base URL an application's backend library is configured with.
Provenance
- Content digest
- sha256:d302889e84873ceaaac42afd223929bdbf7e84058eaa81235f41aeb50b3cc394
- Published
- 2026-11-10T10:13:55Z
- Signing identity
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signature
- Officialapplication/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:8df4006d1413070892da7da543abae6340c461d313674be6015c0ecae3dd1408
Reference at this version
oci://hub.aggrega.ai/component/core/security/supertokens:1.0.0Developer parameters
Values the developer sets in the Aggregate.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| access_token_validity_seconds | integer (min 1) | 3600 | no | How long an access token stays valid, in seconds. A shorter window narrows how long a stolen token is useful and costs a refresh round trip more often. |
| refresh_token_validity_minutes | integer (min 1) | 144000 | no | How long a refresh token stays valid, in minutes. This is the outer bound on a session — once it expires the user signs in again, whatever the access token says. |
| password_hashing_algorithm | string (BCRYPT | ARGON2) | BCRYPT | no | Algorithm the core hashes stored passwords with. Changing it on an installation that already holds users rehashes each password the next time that user signs in, so both algorithms stay readable during the transition. |
| telemetry_enabled | boolean | true | no | Send the project's own anonymous usage telemetry. Turned off, the core reports nothing outward and every other behaviour is unchanged. |
Operator sizing
Infrastructure sizing the operator tunes per environment.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| port | integer (min 1024, max 65535) | 3567 | no | Port the core serves its HTTP API on; consumers connect here. Most operators should omit this and let the Recipe assign the default (3567). |
| engine_version | string | 12.1.1 | no | Core container image tag. |
| log_level | string (DEBUG | INFO | WARN | ERROR | NONE) | INFO | no | Log verbosity of the core. |
| compute | object | — | no | — |
| overrides | object (open) | — | no | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
Output contract
Values this component publishes to consumers over the uses topology.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| host | string | — | yes | In-cluster DNS name of the Service fronting the authentication core. Only an application's own backend reaches it, so this name is not an address to publish to browsers. |
| port | integer | — | yes | TCP port that Service accepts backend requests on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default. |
| endpoint | string | — | yes | Full base URL of the core's HTTP API, with the host and the port already composed. It is the value one of the project's backend client libraries takes as its connection URI. |
| protocol | string | — | no | URL scheme to reach `host` and `port` over, for a consumer composing its own address rather than reading `endpoint`. |
Uses sockets
The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.
backend
- Selector
- component.aggrega.ai/category=datastore
- Inject
- env
Slots each connection through this socket may fill
| Slot | Selector | Required | Inject | Sensitive | Description |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | no | env | yes | Password the core authenticates to the relational backend this connection reaches with, delivered as an env secret reference so the value never appears in the rendered manifest. Unattached, helm/supertokens emits the development literal `apppass`, the default the standard-library relational Recipes leave in place, which is what makes a Release with nothing attached render and run; this catalog publishes it, so every Release that leaves the slot unattached shares that password. |
Attachment slots
Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.
| Slot | Selector | Required | Inject | Sensitive | Description |
|---|---|---|---|---|---|
| api_key | feature.aggrega.ai/kind=secret | no | env | yes | API key a caller must present to reach the core. The core issues none by default and accepts every caller that can reach its address, so attach one here wherever anything beyond the application's own backend can reach it. Unattached, no key is emitted and the core stays open to whatever the network lets through. |
Self-inject allowlist
env
Relationships
Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.
Uses
- usesuses socket «backend»
component.aggrega.ai/category=datastore
Attachment slots: credential
core/datastore/chroma v1.0.0 →core/datastore/cognee v1.0.0 →core/datastore/documentdb v1.0.0 →core/datastore/elasticsearch v1.0.0 →core/datastore/etcd v1.0.0 →core/datastore/ferretdb v1.0.0 →core/datastore/mariadb v1.0.0 →core/datastore/mariadb-operator v1.0.0 →core/datastore/memcached v1.0.0 →core/datastore/milvus v1.0.0 →core/datastore/mysql v1.0.0 →core/datastore/mysql-innodb-cluster v1.0.0 →core/datastore/mysql-operator v1.0.0 →core/datastore/opensearch v1.0.0 →core/datastore/pgvector v1.0.0 →core/datastore/postgres v1.0.0 →core/datastore/qdrant v1.0.0 →core/datastore/redis v1.0.0 →core/datastore/timescaledb v1.0.0 →core/datastore/valkey v1.0.0 →core/datastore/weaviate v1.0.0 →
Used by
uses socket «auth_core»
uses socket «auth_core»
uses socket «auth_core»
uses socket «auth_core»
uses socket «upstream»
uses socket «forward_target»
uses socket «scrape_target»
uses socket «store»
uses socket «jailbreak_detection»
applies to
applies to
applies to
applies to
applies to
applies to
applies to
implements