search

flowable / flowable-engine

A compact and highly efficient workflow and Business Process Management (BPM) platform for developers, system admins and business users.
https://www.flowable.org
Apache License 2.0
7.6k stars 2.55k forks source link

Task login redirect loop but other apps are fine #1043

Open sDLsystem opened 6 years ago

sDLsystem commented 6 years ago

All 6.3 apps work well, except flowable-task which keeps redirecting to the login page: (a) admin username/password are correct; (b) using nginx into a virtual machine but addresses look fine; (c) admin belongs to the "Privileges/workflow app" (idm); (d) flowable-ui-task-app and application.properties seem fine comparing with the other apps; (e) other applications login/logout without problems; (f) no ERROR message in Catalina.out and flowable-task.log (log4j); (g) a fresh h2 database do not change the behaviour.

Many attempts of changing configurations and reinstalls without success. Is it a Spring token/cookie issue? Any idea how to solve? Thks

sDLsystem commented 6 years ago

Added also to Flowable Forum but needs moderation....

Heurazio commented 6 years ago

Can you post your config, please? I had similar errors because I delete the default administrator account (there seems to be an error in the permissions).

spaceghost69 commented 5 years ago

Same problem here. Changed the admin password and now I am unable to log in to any app except the user manager. Redirect loop continues back to IDM:

http://localhost:8080/flowable-idm/#/login?redirectOnAuthSuccess=true&redirectUrl=http:%2F%2Flocalhost:9999%2Fflowable-task%2Fworkflow%2F

I have reverted all flowable-default.properties and application.properties, rebuilt the flowable stack from source multiple times and nothing helps.

Is there a possibility the configuration can be centralized and externalized? Multiple flowable-default.properties files and hard-coded defaults in the codebase make it very difficult to change settings across apps.

filiphr commented 5 years ago

Is there a possibility the configuration can be centralized and externalized? Multiple flowable-default.properties files and hard-coded defaults in the codebase make it very difficult to change settings across apps.

If you are deploying in a tomcat you can define a single application.properties in the tomcat lib folder and all apps will use that. The idea of the flowable-default.properties is for us to provide some sane and to show some examples. You should not be modifying that file. application.properties has a priority over the flowable-default.properties.