Skip to content

feat: token exchange endpoint and documentation - #258

Open
taleodor wants to merge 1 commit into
CycloneDX:mainfrom
relizaio:2026-08-token-auth-endpoint
Open

feat: token exchange endpoint and documentation#258
taleodor wants to merge 1 commit into
CycloneDX:mainfrom
relizaio:2026-08-token-auth-endpoint

Conversation

@taleodor

Copy link
Copy Markdown
Contributor

Implements /token endpoint and corresponding documentation. The endpoint is not required for an open (no-auth TEA server), but if auth is present, the /token endpoint is required. If /token endpoint is used, at least HTTP Basic authentication must be supported, while there are other options.

Signed-off-by: Pavel Shukhman <pavel@reliza.io>
@taleodor
taleodor requested review from madpah and oej as code owners August 26, 2026 01:17

@oej oej left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good work, just some smaller questions

Comment thread auth/readme.md
## The token endpoint

The token endpoint is `POST /token`, relative to the TEA API base URL, and is defined in
[the OpenAPI specification](../spec/openapi.yaml). It is an OAuth 2.0 token endpoint as defined

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this link survive the official doc process (ECMA docs) ?

Comment thread auth/readme.md
Token lifetime, storage, rotation, and revocation are implementation matters and are deliberately
not specified. Two rules keep clients simple in spite of that:

* Servers __should__ return `expires_in`, so that a client can obtain a new token before the current

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a header, part of the JWT or?

@oej

oej commented Aug 26, 2026

Copy link
Copy Markdown
Collaborator

If a client connects to a server that has no "/token" endpoint and no auth - will it receive a 404 which feels weird.

i would like that every TEA service has /token endpoint and if no auth is in play, simply return "200 ok"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants