Login

Login 3.0 allows users to connect via social identity providers such as Facebook, Google, or Apple. All configurations, including social network connections, are managed through the UPBOND team.

To authenticate users with a social provider, make a GET call to the /authorize endpoint. It will return a 302 redirect to the appropriate social provider's sign-in page.

GET <https://auth3.upbond.io/authorize>?
  response_type=code|token&
  client_id=${account.clientId}&
  redirect_uri=${account.callback}&
  state=STATE&
  ADDITIONAL_PARAMETERS

Request Parameters

Parameter	Description
response_type Required	Specifies the token type. Use code for server side flows and token for application side flows
client_id Required	The client_id of your application
redirect_uri Required	The URL to which Login 3.0 will redirect the browser after authorization has been granted by the user.
state Recommended	An opaque value the application adds to the initial request that the authorization server includes when redirecting back to the application. This value must be used by the application to prevent CSRF attacks.
ADDITIONAL_PARAMETERS	Append any additional parameter to the end of your request, and it will be sent to the provider. For example, access_type=offline for Google Refresh Tokens.

Remarks

• If response_type=token, after the user authenticates, the application will receive an Access Token and ID Token in the address. This is used for Single-Page Apps and Native Mobile SDKs.