brazabr
commented
2 years ago Another alternative to this would be a custom scope CRUD section where we could setup any scope and link it to entities/applications/users and leverage the permissions in FusionAuth to do its things.
I found this issue in the repo already:
Support named entities
Problem
Entities include a textual description, but the names themselves are required to be UUIDs. When explaining to customers how to perform the client credentials grant, these UUIDs are confusing because they are, well, random.
Solution
Keep the automatically-generated UUID as the default, but allow any unique string as a name. That way users can request meaningful scopes such as "my_api" or "myserver.company.com".
Alternatives/workarounds
None. We're currently including the entity UUIDs in our documentation and hoping customers copy them correctly.
Related
Community guidelines
All issues filed in this repository must abide by the FusionAuth community guidelines.
How to vote
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.