Halaman ini diterjemahkan oleh mesin. Baca versi asli dalam bahasa Inggris.

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.

Asal-usul

ResmiDitandatangani oleh identitas penandatangan yang diakui katalog ini sebagai penerbit resmi.
Digest konten
sha256:d302889e84873ceaaac42afd223929bdbf7e84058eaa81235f41aeb50b3cc394
Dipublikasikan
2026-11-10T10:13:55Z
Identitas penandatangan
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Tanda tangan

  • Resmiapplication/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

Referensi pada versi ini

oci://hub.aggrega.ai/component/core/security/supertokens:1.0.0

Parameter pengembang

Nilai yang ditetapkan pengembang di Aggregate.

NamaTipeBawaanWajibDeskripsi
access_token_validity_secondsinteger (min 1)3600tidakHow 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_minutesinteger (min 1)144000tidakHow 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_algorithmstring (BCRYPT | ARGON2)BCRYPTtidakAlgorithm 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_enabledbooleantruetidakSend the project's own anonymous usage telemetry. Turned off, the core reports nothing outward and every other behaviour is unchanged.

Penentuan ukuran oleh operator

Ukuran infrastruktur yang disesuaikan operator untuk setiap lingkungan.

NamaTipeBawaanWajibDeskripsi
portinteger (min 1024, max 65535)3567tidakPort the core serves its HTTP API on; consumers connect here. Most operators should omit this and let the Recipe assign the default (3567).
engine_versionstring12.1.1tidakCore container image tag.
log_levelstring (DEBUG | INFO | WARN | ERROR | NONE)INFOtidakLog verbosity of the core.
computeobject—tidak—
overridesobject (open)—tidakProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Kontrak keluaran

Nilai yang dipublikasikan komponen ini kepada konsumen melalui topologi uses.

NamaTipeBawaanWajibDeskripsi
hoststring—yaIn-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.
portinteger—yaTCP 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.
endpointstring—yaFull 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.
protocolstring—tidakURL scheme to reach `host` and `port` over, for a consumer composing its own address rather than reading `endpoint`.

Soket uses

Soket dependensi yang menjadi jalur koneksi komponen ini. Target setiap koneksi yang dihubungkan melalui sebuah soket harus memenuhi selektor labelnya, dan setiap koneksi dapat membawa lampiran pada slot yang dideklarasikan soket tersebut. Slot wajib harus diisi oleh setiap koneksi yang dihubungkan oleh Aggregate atau Release melalui soket tersebut.

backend

Selektor
component.aggrega.ai/category=datastore
Injeksi
env

Slot yang dapat diisi oleh setiap koneksi melalui soket ini

SlotSelektorWajibInjeksiSensitifDeskripsi
credentialfeature.aggrega.ai/kind=secrettidakenvyaPassword 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.

Slot lampiran

Titik pengikatan bernama tempat sebuah Feature dilampirkan ke komponen ini. Selektor sebuah slot membatasi Feature mana yang dapat mengisinya, dan daftar injeksinya menyebutkan cara materi Feature dapat dikirimkan. Slot wajib harus terikat pada setiap instans, melalui lampiran pada instans tersebut atau pada cakupan di atasnya, dan slot sensitif dideklarasikan untuk menangani materi rahasia. Sebuah Feature juga dapat dilampirkan dengan nama yang tidak dideklarasikan oleh slot mana pun.

SlotSelektorWajibInjeksiSensitifDeskripsi
api_keyfeature.aggrega.ai/kind=secrettidakenvyaAPI 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.

Daftar izin injeksi mandiri

env

Relasi

Sisi bertipe ke dan dari entitas lain yang dipublikasikan. Referensi tanpa target yang dipublikasikan ditampilkan sebagai sisi yang terputus, bukan sebagai tautan.

Menggunakan

Digunakan oleh

Referensi konsep Component →

Katalog Aggrega — indeks terbuka berisi komponen, fitur, resep, dan plugin yang merendernya.

Dibangun dengan sistem desain Aggrega yang digunakan bersama.

Privasi