Attach an IAM permission policy as a scope to a Vultr OAuth application to define the access it requests, using the Vultr Console or the Vultr REST API.
A scope defines the permissions your OAuth application requests from the customers who authorize it. Each scope is an IAM permission policy from your own organization. When you attach a policy, Vultr saves a permanent copy that backs the scope. The copied policy is always read-only, and the original policy is also read-only while it is attached as a scope.
Follow this guide to attach a scope to an OAuth application using the Vultr Console and the Vultr API. An application must have at least one scope before you can submit it for review.
Attaching a scope requires the organization's root user. A non-root user receives an HTTP 403 Forbidden response. An OAuth application supports one scope at a time. Detach the existing scope before attaching a different one. Create an IAM policy first if you do not already have one. You can change the scope only while the application is in Draft or Rejected status. A PendingReview or Active application is locked.
Log in to the Vultr Console.
Click the organization name in the top navigation bar.
Click Manage Organization.
Click OAuth Applications.
Click the Edit icon next to the application, open its management page, or click Create OAuth App to set the scope during creation.
Under Permission Policy, use the search field to find a policy and select it.
Click Save as Draft to keep the application editable, or Send for Review to submit it for review.
The selected policy is saved as a read-only copy that backs the application's permission scope. The copy is always read-only, and the original policy is read-only while it is attached.
0 Comments
Be the first to comment and share your perspective with the community.