Can login in IDM but unable to login to Flowable Apps(Admin,Modeler and Task) - Flowable v6.4.1

We are deploying Flowable BPM v6.4.1 on AWS , we can’t login to Task, Modeler or Admin They keep redirecting to the IDM login page. I can ,however,login to IDM itself,

and see the users.I am not able to replicate this issue in local though for the same build.

I could find this relevant link for this issue but it does not help either -

Can you please help us what could be the issue ? In case of any additional info required,please let me know

Hi @Anand

It’s hard to help you without seeing your configuration but maybe you change admin password?
Have you tried this Redirect issue at login ?

there are no change in the configuration admin password is same as earlier all the configurations are same except now we are using mysql version 8 and admin properties file configuration.

This is needed to force use of JDK proxies instead of using CGLIB


The default domain for generating ObjectNames must be specified. Otherwise when multiple Spring Boot applications start in the same servlet container

all would be created with the same name (com.zaxxer.hikari:name=dataSource,type=HikariDataSource) for example


Expose all actuator endpoints to the web

They are exposed, but only authenticated users can see /info and /health abd users with access-admin can see the others


Full health details should only be displayed when a user is authorized

Only users with role access-admin can access full health details

Spring prefixes the roles with ROLE_. However, Flowable does not have that concept yet, so we need to override that with an empty string

H2 example (default)







#Mysql Connection
#spring.datasource.username={MYSQL_USER} #spring.datasource.password={MYSQL_PASSWORD}



If uncommented, the datasource will be looked up using the configured JNDI name.

This will have preference over any datasource configuration done below that doesn’t use JNDI

Eg for JBoss: java:jboss/datasources/flowableDS


Set whether the lookup occurs in a J2EE container, i.e. if the prefix “java:comp/env/” needs to be added if the JNDI

name doesn’t already contain it. Default is “true”.


Connection pool (see

10 minutes


5 minutes


test query for H2, MySQL, PostgreSQL and Microsoft SQL Server

#spring.datasource.hikari.connection-test-query=select 1

test query for Oracle

#spring.datasource.hikari.connection-test-query=SELECT 1 FROM DUAL

test query for DB2

#spring.datasource.hikari.connection-test-query=SELECT current date FROM sysibm.sysdummy1

Default REST endpoint configs

Process engine Process app Process REST config

CMMN engine CMMN app CMMN REST config

App engine App app App REST config

DMN engine DMN app DMN REST config

Form engine Form app Form REST config

Content engine Content app Content REST config

Passwords for rest endpoints and master configs are stored encrypted in the database using AES/CBC/PKCS5PADDING

It needs a 128-bit initialization vector (

and a 128-bit secret key represented as 16 ascii characters below

Do note that if these properties are changed after passwords have been saved, all existing passwords

will not be able to be decrypted and the password would need to be reset in the UI.,FORWARD,ASYNC${FLOWABLE_IDM_URL}/flowable-idm