Connect and verify a Forgejo service identity #11

Open
opened 2026-07-14 22:32:17 -04:00 by caleb-brown · 0 comments
Owner

What to build

A Temper Operator can connect a Forgejo host using a dedicated service account and repository-scoped personal access token, then verify the host, token, and accessible repository boundary.

Acceptance criteria

  • An Operator can configure a Forgejo host and repository-scoped PAT without an OAuth flow.
  • The PAT is encrypted, never redisplayed, omitted from logs, and never forwarded across an origin-changing redirect.
  • Connection testing identifies the Forgejo version and verifies the API capabilities and permissions required for repository discovery and review publication.
  • Accessible repositories can be listed without implying permission to repositories outside the PAT's scope.
  • Unsupported Forgejo versions and under-scoped or revoked PATs produce explicit remediation guidance.
  • The prototype OAuth ADR is superseded and the domain glossary reflects the PAT-backed Forgejo connection model.
  • Forgejo adapter contract tests cover authentication, version detection, pagination, permission failure, and token revocation.

Blocked by

  • #9 — Boot a secure Temper Deployment
## What to build A Temper Operator can connect a Forgejo host using a dedicated service account and repository-scoped personal access token, then verify the host, token, and accessible repository boundary. ## Acceptance criteria - [ ] An Operator can configure a Forgejo host and repository-scoped PAT without an OAuth flow. - [ ] The PAT is encrypted, never redisplayed, omitted from logs, and never forwarded across an origin-changing redirect. - [ ] Connection testing identifies the Forgejo version and verifies the API capabilities and permissions required for repository discovery and review publication. - [ ] Accessible repositories can be listed without implying permission to repositories outside the PAT's scope. - [ ] Unsupported Forgejo versions and under-scoped or revoked PATs produce explicit remediation guidance. - [ ] The prototype OAuth ADR is superseded and the domain glossary reflects the PAT-backed Forgejo connection model. - [ ] Forgejo adapter contract tests cover authentication, version detection, pagination, permission failure, and token revocation. ## Blocked by - [#9](https://git.caleb-brown.dev/caleb-brown/temper/issues/9) — Boot a secure Temper Deployment
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
caleb-brown/temper#11
No description provided.