From 3fc4e4cdc860d47baf24facf0e2d3751d2de6b26 Mon Sep 17 00:00:00 2001 From: Derek McGowan Date: Fri, 12 Feb 2016 14:35:38 -0800 Subject: [PATCH] Add resource scope list definition Allow providing multiple scopes in a single scope string Signed-off-by: Derek McGowan (github: dmcgowan) --- docs/spec/auth/scope.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/spec/auth/scope.md b/docs/spec/auth/scope.md index 3bc941c18..353451921 100644 --- a/docs/spec/auth/scope.md +++ b/docs/spec/auth/scope.md @@ -73,16 +73,17 @@ always derived from the passed in credentials or refresh token. When using a refresh token the passed in audience must match the audience defined for the refresh token. The audience (resource provider) is provided using the `service` field. Multiple resource scopes may be provided using multiple `scope` -fields. The fields may be passed in as either `GET` query parameters or `POST` -form parameters. +fields on the `GET` request. The `POST` request only takes in a single +`scope` field but may use the resource scope list format to specify +multiple resource scopes. ### Resource Scope Grammar ``` -resourcescope := resourcetype ":" resourcename ":" resourceactions +resourcescopelist := resourcescope [ ',' action ]* [ ',' resourcescope]* +resourcescope := resourcetype ":" resourcename ":" action resourcetype := /[a-z]*/ resourcename := component [ '/' component ]* -resourceactions := action [ ',' action ]* action := /[a-z]*/ component := alpha-numeric [separator alpha-numeric]* alpha-numeric := /[a-z0-9]+/