Oauth Callback
const url = 'https://example.com/auth/oauth/example/callback';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/auth/oauth/example/callbackHandle IdP callback: exchange code, find/create user, issue JWT, redirect to frontend.
Phase 268 H-27: the frontend redirect carries access tokens in the URL
fragment. Without explicit-config resolution, an attacker controlling
X-Forwarded-Host could steer the post-callback redirect to
attacker.com and capture the tokens. Force explicit-config resolution
by passing for_external_use=True.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Responses
Section titled “ Responses ”Successful Response
Bad request — invalid query parameters or payload
Unauthorized — missing or invalid credentials
Forbidden — caller lacks access to this resource
Not found
Validation error
Too many requests — retry after the advertised interval
Headers
Section titled “Headers ”Seconds until the request may be retried
Internal server error
Service unavailable — the database could not serve the request