How to address authorization in v3.1 about wolkenkit HOT 3 CLOSED

Hi @smiccoli 👋

Thanks for bringing up this issue, and for your interest in wolkenkit – and of course, thanks as well for the nice words and the great feedback 😊

Your description of how authorization works in 3.x and 4.0 is correct, and it's also correct that the 4.0 version is way more flexible. Actually, since we are almost done with 4.0, I would not recommend to start developing with 3.x any more.

Anyway, taking 3.x as granted for the moment, the suggested solution would be to store things such as groups, roles, … in the identity provider, so that you get it as part of the user's token, and then check for the appropriate claims in the command handler.

This works, as long as you do not need dynamically set up groups at runtime (but talking about junior and senior editors, this seems to be pretty stable).

Does this help? (If not, please reach out to me via email to golo [dot] roden [at] thenativeweb [dot] io).

Have a nice day,

Golo

from wolkenkit.

Indeed it clarifies a lot, as the user token was already including the user's groups and the solution in command handler looks quite simple.

Thanks a lot!

from wolkenkit.

Glad I could help 😊

from wolkenkit.