Skip to content

Clarify hosted OAuth backend boundary #182

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Saga4 wants to merge 1 commit into
base: codex/connector-authority-public
Choose a base branch
from
+13 −0
Open

Clarify hosted OAuth backend boundary #182

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/oauth-architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,3 +52,16 @@ Postgres.
Hosted connectors may consume `locality-auth-core` for IDs and scope profiles,
but hosted availability, tenant binding, finalization, grants, and jobs remain
private runtime responsibilities.

## Backend Image Boundary

The public `apps/oauth-service` broker is the desktop/local-direct OAuth helper.
It completes provider authorization through localhost and must not be deployed
as the hosted credential authority for enterprise/admin sources.

Hosted/admin OAuth is a backend process mode in `locality-internal`. That mode
owns tenant-bound intents, provider callbacks, managed secret references,
Postgres finalization, and worker handoff. Keeping the boundary explicit lets
the public repo share connector identity and callback vocabulary without
shipping hosted tenant authorization, Secrets Manager policy, or admin
credential lifecycle code.
Loading