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.
Procedencia
- Digest del contenido
- sha256:d302889e84873ceaaac42afd223929bdbf7e84058eaa81235f41aeb50b3cc394
- Publicado
- 2026-11-10T10:13:55Z
- Identidad de firma
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Firma
- Oficialapplication/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
Referencia en esta versión
oci://hub.aggrega.ai/component/core/security/supertokens:1.0.0Parámetros del desarrollador
Valores que el desarrollador establece en el Aggregate.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| 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. |
Dimensionamiento del operador
Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| 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. |
Contrato de salida
Valores que este componente publica para los consumidores a través de la topología uses.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| host | string | — | sí | 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 | — | sí | 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 | — | sí | 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`. |
Sockets uses
Los sockets de dependencia a través de los cuales se conecta este componente. El destino de cada conexión cableada a través de un socket debe satisfacer su selector de etiquetas, y cada conexión puede llevar un acoplamiento en los slots que declara el socket. Cada conexión que el Aggregate o la Release cablea a través del socket debe llenar los slots obligatorios.
backend
- Selector
- component.aggrega.ai/category=datastore
- Inyección
- env
Slots que cada conexión a través de este socket puede llenar
| Slot | Selector | Obligatorio | Inyección | Sensible | Descripción |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | no | env | sí | 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. |
Slots de acoplamiento
Puntos de enlace con nombre en los que una Feature se acopla a este componente. El selector de un slot restringe qué Feature puede llenarlo y su lista inject indica cómo puede entregarse el material de la Feature. Un slot obligatorio debe estar enlazado en cada instancia, mediante un acoplamiento en la instancia o en un ámbito superior, y un slot sensible se declara para manejar material secreto. Una Feature también puede acoplarse con un nombre que ningún slot declara.
| Slot | Selector | Obligatorio | Inyección | Sensible | Descripción |
|---|---|---|---|---|---|
| api_key | feature.aggrega.ai/kind=secret | no | env | sí | 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. |
Lista de permitidos de autoinyección
env
Relaciones
Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.
Usa
- usausa el socket «backend»
component.aggrega.ai/category=datastore
Slots de acoplamiento: 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 →
Usado por
usa el socket «auth_core»
usa el socket «auth_core»
usa el socket «auth_core»
usa el socket «auth_core»
usa el socket «upstream»
usa el socket «forward_target»
usa el socket «scrape_target»
usa el socket «store»
usa el socket «jailbreak_detection»
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
implementa