User Authorization issue

[brepine]

I’m trying to create a read-only user for Cockpit/Tasklist/Admin similar to here:

Read-only operator mode

Dear Camunda Folks, Would appreciate your advise on implementing a read-only Operator role in Cockpit. We are looking for a way to provide “reporting” capability, while avoiding segregation of duty conflicts. What would be a sufficient level of authorisations to assign a group READ_ONLY access to cockpit? Would be also happy to hear your thoughts on lessons learnt. Thank you in advance. Best regards, Ilya

But when I create the new user it seems to have all of the privileges of the camunda-admin user even tho the new user does not exist in that group.
No matter what authorizations I try to grant the new user none seem to take effect and it always appears that they have full camunda-admin privileges.
Most specifically I’m trying to remove access to the Delete process Action from the Cockpit.

I’ve also followed the examples listed here to no avail:

Authorization Management | docs.camunda.org

Is there a configuration property I’m missing?

Camunda ver 7.14.0-ee running in a WildFly container

[brepine]

Discovered there is an authorizationEnabled property that is false by default. When set to true I see the expected behavior.

[amir133]

@brepine How can Enable authorizationEnabled ? where is this property?

[StephanHaarmann]

If you’re using a spring boot-based version of Camunda (i.e., camunda run), the property is within your configuration, i.e., default.yml or application.yml.
There you can add

camunda.bpm:
  authorization:
    enabled: true

[brepine]

@brepine

authorizationEnabled

For our WildFly environment we enabled this property in the process-engine configuration of the standalone.xml