I created a new group with the admin, called Users. I did not assigned any authorization to them. So I created a user, I give it the group Users and I login with that user. Well, it has the same powers of an admin. How can it be?
PS: by default, there’s no “All Tasks” filter. This is intentional or the problem is I’m using Postgres and Hibernate does not support Postgres LOBs?
That should not happen. what Version of Camunda are you running?
Can you provide a screenshot of the Application Authorizations page as well as the Groups Page of the User?
This is intentional, as we start Camunda with an empty database. Clicking ‘Create a simple filter’ will generate the ‘All Tasks’ filter for you.
PS: well, as you create the db, you can add a row for a “All Tasks” filter. The newbie is really confused about the fact no task is visible even if there are ones.
PPS: and it should undeletable IMHO.
A lot of people use the engine and don’t use the filters at all, so it’s better to give the user a choice with the default adding nothing in case it’s not required.
Mmmmhhh… it seems to me the same arguments of rich people about public healthcare
Jokes apart, ok, a lot of people don’t need tasks and will never land on the page. But the people that need tasks usually expects to see his tasks, not to create a filter for viewing tasks. It’s misleading, since no one expects that for viewing ALL tasks you have to create a FILTER.
Furthermore, what problem can cause having the All Tasks filter created by default?
I disagree that people who use task list need the all tasks filter. From my experience when implemented for any kind of real use case the All Tasks filter is often removed or never added. Tasks are assigned to groups or users and it’s not often the case that task workers are presented with a list of ALL tasks across the whole engine to choose from.
with regard to your point about it confusing people who are maybe just having a look at camunda? Well thats why we add filters (including the all tasks filter) to the default disro you would find on the download page:
The only reason would not have seen filters is because you would have chosen to startup a completely fresh distro without any data.
Ok, but what’s the problem of creating such a filter by default also in a fresh Spring Boot installation? If the user does not need it, it can remove it. But newbies like me will be not confused by the fact they see no tasks even if it should be one. An UX designer will suicide itself…
From my perspective the default springboot installations should be as clean as possible, for a number of reasons including the fact that we don’t know how it’s intended to be used.
We have the archetype so that you can setup something to help you explore functionality.
Can I only add as final thought that for all the other categories, Deployments, Processes, Users and Groups, all the items are displayed by default? Tasks are the only exception and it’s confusing. No sane man will expect something like this as default behavior.
I understand Spring is intended to be a clan installation completely customizable, without any defaults. But I think that a filter that can be removed can’t hurt the sensibility of the more purist of Spring dev.
sorry for the delay, you need to explicitly enable the authorization: camunda.bpm.authorization.enabled=true
please check the spring boot docs for reference