OAuth scopes are a way to define data and permissions on data. For example, there are scopes defined for "Read-only access to Google Calendar" and "Access to Cloud Platform". Users can consent to a scope for an application, giving it permission to access that data on their behalf.
OAuth scope specifications should be fairly coarse grained; a user will need to see and understand the text description of what your scope means.
In most cases: use one or at most two OAuth scopes for an entire family of products. If your product has multiple APIs, you should probably be sharing the OAuth scope across all of those APIs.
When you need finer grained OAuth consent screens: talk with your product management about how developers will use them in practice.
Please note that even though each of the canonical scopes is enough for a request to be accepted and passed to the backend, a request can still fail due to the backend requiring additional scopes or permissions.
- canonicalScopes ↔ String
The list of publicly documented OAuth scopes that are allowed access. An
OAuth token containing any of these scopes will be accepted. [...]
read / write
- hashCode → int
The hash code for this object.
- runtimeType → Type
A representation of the runtime type of the object.
) → Map< String, Object>
Invocation invocation) → dynamic
Invoked when a non-existent method or property is accessed.
) → String
Returns a string representation of this object.
dynamic other) → bool
The equality operator.