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.
来源
- 内容摘要
- sha256:d302889e84873ceaaac42afd223929bdbf7e84058eaa81235f41aeb50b3cc394
- 发布时间
- 2026-11-10T10:13:55Z
- 签名身份
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
签名
- 官方application/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
此版本的引用
oci://hub.aggrega.ai/component/core/security/supertokens:1.0.0开发者参数
开发者在 Aggregate 中设置的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| access_token_validity_seconds | integer (min 1) | 3600 | 否 | 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 | 否 | 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 | 否 | 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 | 否 | Send the project's own anonymous usage telemetry. Turned off, the core reports nothing outward and every other behaviour is unchanged. |
运维规格
运维人员按环境调整的基础设施规格。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| port | integer (min 1024, max 65535) | 3567 | 否 | 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 | 否 | Core container image tag. |
| log_level | string (DEBUG | INFO | WARN | ERROR | NONE) | INFO | 否 | Log verbosity of the core. |
| compute | object | — | 否 | — |
| overrides | object (open) | — | 否 | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
输出契约
此组件通过 uses 拓扑向使用方发布的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| host | string | — | 是 | 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 | — | 是 | 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 | — | 是 | 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 | — | 否 | URL scheme to reach `host` and `port` over, for a consumer composing its own address rather than reading `endpoint`. |
uses 套接字
此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。
backend
- 选择器
- component.aggrega.ai/category=datastore
- 注入
- env
经由此套接字的每个连接可填充的槽位
| 槽位 | 选择器 | 必需 | 注入 | 敏感 | 描述 |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | 否 | env | 是 | 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. |
附加槽位
Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。
| 槽位 | 选择器 | 必需 | 注入 | 敏感 | 描述 |
|---|---|---|---|---|---|
| api_key | feature.aggrega.ai/kind=secret | 否 | env | 是 | 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. |
自注入允许列表
env
关系
与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。
使用
- 使用使用套接字 «backend»
component.aggrega.ai/category=datastore
附加槽位: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 →
被使用
使用套接字 «auth_core»
使用套接字 «auth_core»
使用套接字 «auth_core»
使用套接字 «auth_core»
使用套接字 «upstream»
使用套接字 «forward_target»
使用套接字 «scrape_target»
使用套接字 «store»
使用套接字 «jailbreak_detection»
适用于
适用于
适用于
适用于
适用于
适用于
适用于
实现