Mateusz Urbanek f1cceee8cd
feat: implement authentication support
This feature is Enterprise only (requires BUSL).

Any access to the schematic requires the user to be authenticated
before access.

Moreover, any schematic stores the owner in the schematic, so each
schematic becomes private (owned by the user which created it).

Authentication is configured using a set of usernames and keys
associates with each user (API key).

Co-authored-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
Signed-off-by: Mateusz Urbanek <mateusz.urbanek@siderolabs.com>
2026-04-20 15:54:31 +02:00

7 lines
360 B
Plaintext

# Fixture for authentication configuration in the integration tests.
# alice has two passwords: alicesecret and alicetopsecret
alice:$2a$10$IncF6ZgOKkwL5YrZQZWbb.cxyVnhYj0PZLoTADMmZ9dRNBE0G5XwW
alice:$2a$10$4BZEQoTTUw0a/OXXjTcZMOcfI1Vd33YifMbqhJTurunWXgCuzdIxm
# bob has one password: bobsecret
bob:$2a$10$U9nvzVw56UlJKsnkREoDzessssxqkN0Cck4IecOOZMD.LzaRvNVbG