Skip to content

Authentication Request

The authentication request must be made to the Identity Provider's authentication endpoint, with additional parameters in query string format.

URLs

MethodURLActionDescription
GET/authorizeAuthenticateInitiates the user authentication and authorization flow

Production:

{login-producao}/authorize

Staging:

{login-homologacao}/authorize

Required Parameters

ParameterDescriptionExample
response_typeExpected response typecode
scopeRequested permissionsopenid profile
client_idClient IDexampleclient
redirect_uriRedirect URIhttps://example.com.br/callback

Request Example

Production:

{login-producao}/authorize?response_type=code&scope=openid profile&client_id=exampleclient&redirect_uri=https://example.com.br/callback

Staging:

{login-homologacao}/authorize?response_type=code&scope=openid profile&client_id=exampleclient&redirect_uri=https://example.com.br/callback

In addition to the basic and required parameters, there are additional parameters mentioned in chapters 8 and 9. After receiving the request, the system will proceed with the authentication and authorization process.

Optional Parameters

state

Opaque value used to maintain state between the request and callback. Commonly used for CSRF mitigation.

&state=af0ifjsldkj

nonce

Case-sensitive string used to associate a client session with an id_token and to mitigate Replay attacks.

&nonce=n-0S6_WzA2Mj

id_token_hint and prompt

For authentication without user interaction (when the user already has an active session):

&id_token_hint=<jwt_token>&prompt=none

Flow

  1. User is redirected to the authorization endpoint
  2. System processes authentication and authorization
  3. User is redirected back to the provided redirect_uri
  4. Additional information is returned in query string format

Next Step

After receiving the response, continue to Authentication Response.

Fanbase API Documentation