It may happen, that a user's list of groups is too long. Both in practicality and in terms of token being too large to save in limited spaces (4K limit for cookies for example).
For this reason, it may be useful to request user token with an optional filtering field that will limit the groups to the set of interested values.
Feature
Provide /token/generate rest call (either introduce an optional param there or create another endpoint) where groups filter can be employed.
Consider the practical options for filtering.
From the practical standpoint, prefix filtering should be enough.
Background
It may happen, that a user's list of groups is too long. Both in practicality and in terms of token being too large to save in limited spaces (4K limit for cookies for example).
For this reason, it may be useful to request user token with an optional filtering field that will limit the groups to the set of interested values.
Feature
Provide
/token/generate
rest call (either introduce an optional param there or create another endpoint) where groups filter can be employed.Consider the practical options for filtering. From the practical standpoint, prefix filtering should be enough.
Example [Optional]
/token/generate?group-prefix=abcd-
/token/generate?group-prefix=abcd-|efgh-|something-else-
(/token/generate?group-suffix=-admin
) (/token/generate?group-contains=-ursa-unify-
) (/token/generate?group-regex=\d{4}-\d\d-\d\d
)(just ideas, not all of these need to be implemented if not needed)