You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<entity-permission>
<name>member-view</name>
<entity-type>awa_workspace</entity-type>
<description>Grant the member view </description>
<sql>
SELECT acl.id FROM awa_acl AS acl
WHERE acl.entity_type = :entity_type
AND acl.user_id = :user_id
AND acl.entity_id = 1
AND acl.permission = $permission[member-view]
</sql>
</entity-permission>
if we want to use the permission in an url-policy like:
then the entity-permission is always rejected because when we evaluate it there is no entity-id to evaluate and the permission controller immediately reject the permission even if the SQL query does not make reference to the entity-id.
If the SQL does not references the :entity_id parameter, then the controller should proceed and run the SQL query to check the permission (instead of rejecting without checking).
The text was updated successfully, but these errors were encountered:
When we have an entity permission like:
if we want to use the permission in an url-policy like:
then the entity-permission is always rejected because when we evaluate it there is no entity-id to evaluate and the permission controller immediately reject the permission even if the SQL query does not make reference to the entity-id.
If the SQL does not references the
:entity_id
parameter, then the controller should proceed and run the SQL query to check the permission (instead of rejecting without checking).The text was updated successfully, but these errors were encountered: