Skip to content

Latest commit

 

History

History
19 lines (9 loc) · 868 Bytes

define-scope.md

File metadata and controls

19 lines (9 loc) · 868 Bytes
Raw

Defining a Scope

-Scope values in OAuth2 are arbitrary strings, but in the UAA they normally have a resource id and some level of access (e.g., “read”, “write” and “admin”) separated by a period.

  • The uaa auto populates the "audience" field of the token with the scope names ( sub-string until last index of (dot) ) that you provided in the client registration of the UAA.yml class, and with client Id name.

  • If the token "audience" field doesn't contain the resource id , the resource server will deny access to a resource.

Scope Naming Convention

-Scope in UAA should be defined as resourceId.resourceName_permission

-resourceId and resourceName should always be separated by a period '.'

-resourceName and permission should be separated by a underscore '_'

-All words resourceId, resourceName and permission should follow a Camel Casing