Let's follow up this discussion at the Neptune Community
(this forum will be kept in read-only mode)
We use the frontend/backend split setup. The frontend server is used for the frontend development and to group apps from various backend systems.
As our apps are tied to a backend system (using field RFC destination), we would also like the Tile authorization to be based on backend authorization roles.
-We can reuse the existing authorization model in the backend system and do not need to build a separate one in the frontend server.
-Authorization checks in the Neptune backend class are also handled by authorization checks in the backend. This way we could bundle all authorizations for an App into one single authorization role.
Therefore we would like to have an option to add backend authorization roles to a policy.
This will clearly be a useful feature, and comparing implementation time on our end, with the time needed to replicate all roles and user assignment in Customer systems, this is definitely something we will be looking into.