Fix Authentik WIF token endpoint
This commit is contained in:
parent
5ef4fdef64
commit
8180c3c35a
2 changed files with 33 additions and 1 deletions
|
|
@ -81,6 +81,10 @@ The same change also makes the forge itself the release authority: release tags
|
|||
resolves Nix from those profile paths, and the action builds `.#age` before
|
||||
falling back to `.#agenix`. The decrypt step must not require Python before
|
||||
the Nix CI shell is active.
|
||||
- Authentik-backed Google WIF must exchange tokens against Authentik's OAuth
|
||||
token endpoint, not a provider-slug child path. The helper should prefer an
|
||||
explicit `BURROW_AUTHENTIK_WIF_TOKEN_ENDPOINT`, then OIDC discovery, then the
|
||||
Authentik `/application/o/token/` fallback derived from the configured issuer.
|
||||
- Produce unsigned Apple validation artifacts when signing is absent, but require signing for an App Store requested iOS release and for a Sparkle tester release. Uploadable artifacts are produced only after provisioning profiles can be synced from App Store Connect credentials and the relevant Apple certificate is proven to match the selected Google KMS key.
|
||||
- Resolve release credentials through age/agenix before signed Apple lanes run. Forgejo secrets should carry only the runner age identity fallback and the Authentik WIF client secret until OpenBao can mint the runner token directly. App Store Connect keys and signing certificates live as sealed files under `secrets/`.
|
||||
- Persist the forge runner SSH key as `/var/lib/forgejo-runner-agent/age_keystore` and export `BURROW_RUNNER_AGE_IDENTITY_PATH` so jobs can resolve agenix identities without embedding long-lived material in every workflow.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue