When creating a client using the latest build of UAA, the scopes are not validated. The UAA is creating the scope with any string we give rather than validating the scopes existence within UAA. Is it any limitation that UAA has to validate scopes?, as grant types are being validated by the CLI at the same time.
This is similar PR opened for UAAC at https://github.com/cloudfoundry/cf-uaac/issues/64
When creating a client using the latest build of UAA, the scopes are not validated. The UAA is creating the scope with any string we give rather than validating the scopes existence within UAA. Is it any limitation that UAA has to validate scopes?, as grant types are being validated by the CLI at the same time.