So it looks like if the scope name starts with `uaa.` we ignore it at the
time of app authorization. I will create a story in our backlog to
investigate why that is the case. As a workaround if you want the scope to
end up in the access token you can autoapprove that scope in the client
configuration in uaa.yml. Example:
https://github.com/cloudfoundry/uaa-release/blob/develop/jobs/uaa/spec#L256

On Wed, Jun 29, 2016 at 2:00 PM, Bryan Perino <Bryan.Perino(a)gmail.com>
wrote:

There are 3 requests to /oauth/authorize. I have saved all 3 as HAR files.

https://dl.dropboxusercontent.com/u/4177525/har-files.zip