Can we improve Client Scopes Condition and make sure that Scope type can be either “default” or “optional” or “both” ? Currently we don’t have value “both”.

Right now, we can already support use-cases like:

• Do something if scope foo is available as default client scope of client triggering the request
• Do something if scope foo is available as optional client scope of client triggering the request and it is used in the scope parameter

But AFAIK we cannot easily support use-case like:

• Do something if scope foo is applied in the request (either automatically as default scope or by the parameter if client has it declared as optional scope)

This means that we cannot support use-case from #37124 easily (due the fact that condition needs to be declared either as “default” scope foo OR “optional” scope foo)