It'is possbile to implement own Security Constraint that can extend other Constraint class (e.g. CrudEntityConstraint) or any other and apply application-wide e.g. to forbid UI edit for all entities. This needs registring with accessConstraintsRegistry.register() method call in some @PostConstruct annotated method and this is done in the following configuration:
This should be described in documentaion and/or cookbook for developers to know how to customize security contranints, e.g. at the following page: https://docs.jmix.io/jmix/security/authorization.html
It'is possbile to implement own Security Constraint that can extend other Constraint class (e.g. CrudEntityConstraint) or any other and apply application-wide e.g. to forbid UI edit for all entities. This needs registring with
accessConstraintsRegistry.register()method call in some @PostConstruct annotated method and this is done in the following configuration:This should be described in documentaion and/or cookbook for developers to know how to customize security contranints, e.g. at the following page: https://docs.jmix.io/jmix/security/authorization.html