Environment:
camunda BPM 7.2.0-alpha5 deployed on Glassfish 3.1.2.2.
Issue:
Via the bpm-platform.xml, I configured two process engines named "tenant1" and "tenant2".
When I try to login to tasklist, it displays the message "Your session has expired. You need to sign in again.". In the browser console, messages cycle through like:
OPTIONS http://localhost:8080/camunda/api/engine/engine/default/filter [HTTP/1.1 401 Unauthorized 7ms]
"Error: cannot OPTIONS /camunda/api/engine/engine/default/filter (401)
[27]</f.prototype.toError@http://localhost:8080/camunda/app/tasklist/scripts/deps.js:9:24475
[27]</f.prototype.setStatusProperties@http://localhost:8080/camunda/app/tasklist/scripts/deps.js:9:24159
f@http://localhost:8080/camunda/app/tasklist/scripts/deps.js:9:22548
d/<@http://localhost:8080/camunda/app/tasklist/scripts/deps.js:9:22978
[28]</n.prototype.emit@http://localhost:8080/camunda/app/tasklist/scripts/deps.js:9:29095
[27]</d.prototype.end/a.onreadystatechange@http://localhost:8080/camunda/app/tasklist/scripts/deps.js:9:26807
" deps.js:5
The login works fine for the admin and cockpit apps. Furthermore, if I change the configuration and rename the process engine "tenant1" in "default", the tasklist login works.
Seems that tasklist relies on an existing "default" process engine.