❔ Implementing security from a web library
We're coding a web library to generate a html CRUD at runtime from a metadata, after a lot of effort the project is getting cool, but now we need to implement security rules for the routes:
Ex: in the DataDictionary area, where the metadata are configured only admin could access, and the MasterData Area would be access to the CRUD Form where logged users would access.
What would be the best strategy to setup this scenario?
Repo:
https://github.com/JJConsulting/JJMasterData
I've been implemented it by adding policy to the routes, but I thought it was too difficult to configure
https://jjconsulting.tech/docs/JJMasterData/articles/authorization.html
Any suggestion will be welcome.
Ex: in the DataDictionary area, where the metadata are configured only admin could access, and the MasterData Area would be access to the CRUD Form where logged users would access.
What would be the best strategy to setup this scenario?
Repo:
https://github.com/JJConsulting/JJMasterData
I've been implemented it by adding policy to the routes, but I thought it was too difficult to configure
https://jjconsulting.tech/docs/JJMasterData/articles/authorization.html
Any suggestion will be welcome.
GitHub
.NET CRUD library with Bootstrap support to create Forms at runtime from a data dictionary. - GitHub - JJConsulting/JJMasterData: .NET CRUD library with Bootstrap support to create Forms at runtime...
