gropius.authorization ​

Provides Authorization related beans which are necessary to check for permissions

Default authorization context

Base gropius authorization context Provides flexibility how to define the userNode

Base class for all NodePermission based AllowRuleGenerators Provides a method which is able to check for a specific permission on a NodePermission for a specific GropiusUser

Permission rule generator used to check if a node is connected via NodePermission.RELATED_TO_NODE_PERMISSION to an NodePermission with NodePermission.ADMIN The Permission must be declared with a parameter containing the max amount of relationships to traverse until the NodePermission

Permission to check that a GropiusUser is connected to a GlobalPermission with the specified Permission Assumes that node is a GropiusUser node Caution: does use the node, not the gropiusUser from the authorization context!

Permission rule generator which checks for a Node that is related via a NodePermission which provides a specific permission (specified by permission.name) to the User. Additional permission names can be provided via the parameters of the Rule. In this case, it is sufficient if ANY of the permissions is granted. Requires a GropiusAuthorizationContext as authorization context

Gets checkPermission of a possibly set GropiusAuthorizationContext and evaluates to false otherwise

Gets the GropiusAuthorizationContext from the DataFetchingEnvironment Assumes that DataFetchingEnvironment.authorizationContext is a GropiusAuthorizationContext

The name of the RelatedToAdminNodePermissionRuleGenerator, used to check if a node is related to a NodePermission with ADMIN via NodePermission.RELATED_TO_NODE_PERMISSION

The name of the RelatedToGlobalPermissionRuleGenerator used to check if a GropiusUser is related to a GlobalPermission

The name of the rule which checks that a Node is related to a NodePermission