ADMIN_PASSWORD={{ lookup('users', 'administrator').password | dotenv_quote }}

ADMIN_USERNAME={{ lookup('users', 'administrator').username | dotenv_quote }}

APP_BASE_URL={{ lookup('tls', application_id, 'url.base') | dotenv_quote }}

BIBER_PASSWORD={{ lookup('users', 'biber').password | dotenv_quote }}

BIBER_USERNAME={{ lookup('users', 'biber').username | dotenv_quote }}

CANONICAL_DOMAIN={{ lookup('domain', application_id) | dotenv_quote }}

LOGOUT_SERVICE_ENABLED={{ lookup('config', application_id, 'services.logout.enabled') | string | lower }}

MATOMO_API_TOKEN={{ lookup('users', 'administrator').tokens['web-app-matomo'] | dotenv_quote }}

MATOMO_BASE_URL={{ lookup('tls', 'web-app-matomo', 'url.base') | dotenv_quote }}

MATOMO_TARGET_ROLES_JSON={{ lookup('roles_with_service', 'matomo') | to_json | dotenv_quote }}

MATOMO_TRACKING_SCOPE={{ lookup('config', application_id, 'services.matomo.tracking.scope') | string | lower }}

OIDC_ISSUER_URL={{ OIDC.CLIENT.ISSUER_URL | dotenv_quote }}


# nocheck: persona-block-rationale — meta/services.yml pins sso.enabled=false: Matomo holds no Keycloak client, so the OIDC round-trip the shared helper waits for never happens; the admin journey is Matomo's native index.php?module=Login form against the local superuser (vars/main.yml MATOMO_ADMIN_*), driven by the role's own auth.spec.js (see README "Persona contract opt-outs").
PERSONA_ADMINISTRATOR_BLOCKED=true

# nocheck: persona-block-rationale — the role provisions exactly one Matomo account, the superuser keyed by MATOMO_ADMIN_USER_KEY in vars/main.yml; there is no per-user provisioning, so biber has no Matomo identity to log in with at all. Matomo instead owns the deny-probe proving biber cannot reach the admin surface (see README "Persona contract opt-outs").
PERSONA_BIBER_BLOCKED=true

SSO_SERVICE_ENABLED={{ lookup('config', application_id, 'services.sso.enabled') | string | lower }}