Sign in
auth

Authorize

Start an OAuth sign-in: where to send the browser, and the state to keep.

A GET, and safe: it reads configuration and mints a random value, writing nothing. Repeating it simply produces another state, and only the one the browser kept is the one it will compare against.

get/v1/auth/oauth/{provider}/authorize

Path parameters

providerstring required

Which OAuth provider to sign in with.

Which OAuth provider to sign in with.

Response

Successful Response

authorization_urlstring required

The provider consent screen to navigate to.

statestring required

An opaque CSRF value to keep for the length of the redirect and compare against the 'state' the provider returns. It is not stored on this deployment, so a callback whose state does not match the one held by the browser that started the flow must be abandoned by the client rather than sent here.

Changes

Changed in 1 of the 133 revisions of this API.1