Docker IDM Redirect URL

Hi,

My problem is the default redirect url:
FLOWABLE_COMMON_APP_IDM-REDIRECT-URL: full url of the IDM app; used for client browser redirection (f.e. http://localhost:8080/flowable-idm)

I connect to a Docker Server over VPN … so the flowable idm’s url is something like 10.8.0.1:8500/flowable-idm …

is it right that i must use the redirect url for http://10.8.0.1:8500/flowable-idm.
So if i am on an other subnet … the redirect doesen’t work… or is there a other solution for the redirect ?

Should container link working with IDM redirect url ?
- FLOWABLE_COMMON_APP_IDM-REDIRECT-URL=http://flowable-idm-app:8080/flowable-idm
if i do so my redirect url looks like

http://flowable-idm-app:8080/flowable-idm/#/login?redirectOnAuthSuccess=true&redirectUrl=http://172.18.0.4:8080/flowable-modeler/

Hi,

Perhaps I don’t understand what the issue is you’re having. But, as you stated, the FLOWABLE_COMMON_APP_IDM-REDIRECT-URL is used for the client browser redirect. This implies that this endpoint must be accessible from the client.
FLOWABLE_COMMON_APP_IDM-URL is used for inter server communication. In other words; this endpoint must be accessible for the other Flowable containers.

Is this the case in your situation?

Regards,

Yvo

ok ok it was my mistake … so its working now. my compose file is attached

Version: '3.6'
services:
  flowable-modeler-app:
image: flowable/flowable-modeler
depends_on:
  - flowable-idm-app
environment:
  - SERVER_PORT=8080
  - SPRING_DATASOURCE_DRIVER-CLASS-NAME=${SPRING_DATASOURCE_DRIVER_CLASS_NAME}
  - SPRING_DATASOURCE_URL=${SPRING_DATASOURCE_URL}
  - SPRING_DATASOURCE_USERNAME=${SPRING_DATASOURCE_USERNAME}
  - SPRING_DATASOURCE_PASSWORD=${SPRING_DATASOURCE_PASSWORD}
  - FLOWABLE_COMMON_APP_IDM-URL=http://flowable-idm-app:8080/flowable-idm
  - FLOWABLE_COMMON_APP_IDM-REDIRECT-URL=http://172.18.0.1:8500/flowable-idm
  - FLOWABLE_COMMON_APP_IDM-ADMIN_USER=${FLOWABLE_COMMON_APP_IDM_ADMIN_USER}
  - FLOWABLE_COMMON_APP_IDM-ADMIN_PASSWORD=${FLOWABLE_COMMON_APP_IDM_ADMIN_PASSWORD}
ports:
  - 8502:8080
entrypoint: ["java", "-jar", "app.war"]

But there is one thing which is a little problem …

If you access the modeler by an other subnet as the redirect is … so modeler is access under http://10.8.01:8502/flowable-modeler … it redirects on the redirect url http://172.18.0.1:8500/flowable-idm … and this results in a permanent redirect … so no login is possible to modeler.

The different Flowable UI apps need to be accessible for the client / browser with the same hostname.
This is needed in order for the browser to read the cookie.
It seems this is the problem you having now.

F.e. a reverse proxy can be used for this.

Regards.

Yvo