Grant a third-party OAuth application access to your Vultr account within your own permissions and receive a one-time authorization code using the API.
Authorizing a third-party OAuth application grants it permission to act on your Vultr account within a defined set of scopes. When you authorize an application, Vultr issues a one-time authorization code that the application exchanges for an access token, and creates a dedicated role that limits the application to only the permissions you consented to.
Follow this guide to authorize a third-party OAuth application using the Vultr Console and the Vultr API.
403 Forbidden response and no access is granted.Active can be authorized only by users on its draft-mode allowlist. Any other user receives an HTTP 403 Forbidden response.redirect_uri must exactly match a callback URL registered to the application, and response_type must be code. Otherwise the request returns an HTTP 400 Bad Request response.The Vultr consent screen appears when a third-party application redirects you to Vultr to authorize it.
Start the connect or sign-in action from the third-party application. It redirects you to the Vultr consent screen.
Sign in to the Vultr Console if you are prompted.
On the Review and Decide screen, review the application, its developer, and the list of permissions it requests.
Click Authorize to grant access, or Decline Authorization to deny it.
A confirmation appears, and the browser redirects back to the application, which exchanges the authorization code for an access token. The application then appears in your authorized applications.
0 Comments
Be the first to comment and share your perspective with the community.