Hii Everyone!!
I have created one group and assigned some users in that group and also provided all authorization just like camunda-admin group has access to all web application(cockpit,tasklist,admin).But these users not able to see any process defination in tasklist to start the instance.
Here I am attaching some screenshot regarding authorization.
Here Lalit user belongs to the student group but still he is not able to create any instance as you can see in the screentshot
Strange…
If you grant full access to “Application”… and full access to “Process Definitions” you should be able to check and start instances in the processes.
Are you sure you added this user to your group?
Isn’t there some exclusive permission for this user, denying access to the processDefinition?
I even just did a test here, in the same scenario and it works correctly.
William Robert Alves
Remembering that… you need to put the “Group ID” in the authorization, not the “Group Name”.
William Robert Alves
Hii @WilliamR.Alves
Thanks for your Reply.Currently I am using latest version of BPMN and even i also tried with camunda version 7.15 with same scenario and facing same issue.
yes i used group id instead of group name.
May i know which version of camunda bpmn you are using??
My version is 7.16 bro.
William Robert Alves
@Lalit_Verma do you have the “authorization.enabled” property on your “application.yml” as true?
Example:
@WilliamR.Alves There is no application.yml file in my camunda-bpmn folder.Can you please share the file location ??
Try to run a test by granting access to the entire Camunda for this group and see if it works… because I find this very strange… it should be working.
Hii @WilliamR.Alves,
Thanks for helping me. Actually at the time of process deployment i was using tenent Id which creates problems. Now i am able to create process instance with other groups in all camunda version except 7.21 .Could you please try this version wheather it is working in your system or not ??
It will really help me a lot.
Thank you!!
Hello! You’re welcome bro 
Do you know that depending on the version you are using, things may have changed in the database structure, right?
And if you don’t run the scripts to update between one version and another, could you experience some incompatibilities or unexpected errors?
This could be one of your current problems, if you haven’t run the scripts to update your DB.
William Robert Alves
In other words, there is no point in just changing the version and testing on other versions without running the scripts to update the database, as you could have several problems.
You must follow the version that is configured in your dependencies file (pom.xml or gradle).
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.