LeoVasanko
84985501f5
- Serve multiple domains (RP IDs) from one instance: host-based dispatch, per-domain credentials and sessions, domains managed at runtime in the admin UI — previously one RP per instance - Cross-domain sign-in via Related Origin Requests: per-domain related-origins list with a served .well-known/webauthn document - Explicit per-domain origin lists with shell-glob wildcards (**. for apex + any subdomain depth, *. for one level), editable in the admin UI with validation and self-lockout guards - Per-domain auth hosts: the account/admin UI can live on a different host per domain, no longer confined to subdomains of a single RP - CLI: 'paskia init <rp-id [rp-name]' initializes or adds a domain to an existing database; 'paskia migrate' converts legacy databases BREAKING CHANGES (v2.0): - Database schema: config is now per-domain and credentials/sessions carry an rp_id — existing databases must be converted with 'paskia migrate' - Origins are now explicit: main implicitly allowed every subdomain of the RP; configure '**.' origins to reproduce that behavior - CLI: the flat '--rp-id/--rp-name/--origin/--auth/--save' flags are replaced by the 'init' and 'migrate' subcommandsReviewed-on: #4
14 lines
519 B
Plaintext
14 lines
519 B
Plaintext
# Setup auth service at /auth/ and remove any Remote-* headers sent by client (for security)
|
|
header -Remote-*
|
|
@auth_api path /auth /auth/*
|
|
handle @auth_api {
|
|
reverse_proxy {$AUTH_UPSTREAM::4401}
|
|
}
|
|
# Paskia-served well-known endpoints: OIDC discovery and WebAuthn Related
|
|
# Origin Requests (must reach paskia even when other /.well-known/* files
|
|
# are served statically)
|
|
@auth_wellknown path /.well-known/openid-configuration /.well-known/webauthn
|
|
handle @auth_wellknown {
|
|
reverse_proxy {$AUTH_UPSTREAM::4401}
|
|
}
|