Limiting Scopes for client resources
For some business logic reasons, we are going to have a SCOPE_VERIFY distinct from the usual SCOPE_READ/WRITE, etc.
We want it such that this scope has to be alone in a request for an authorization code, can't be combined with other scopes.
This will force clients to define at least two client resources in their config, one with all their other authorized grant types and one with only SCOPE_VERIFY.
I'm trying to figure out the best way on the provider end to enforce this restriction, but haven't quite come up with something that doesn't seem hacky/kludgy. So I'm wondering what would be right and proper way to:
1) Never grant an access token (via authorization_code) w/verify combined w/any other scope.
2) Never allow a client w/any scope other than verify to access resources that are SCOPE_VERIFY