It seems session persistence is broken with the Wildfly Client Adapter. I have:
<persistent-sessions/>
in the standalone.xml file under:
<servlet-container name="default">
This was set using the command:
.jboss-cli.sh --connect
--command="/subsystem=undertow/servlet-container=default/setting=persistent-sessions:add()"
However, if I run the command:
.jboss-cli.sh --connect --command="/deployment=myapp.war:redeploy()"
My authenticated session is lost and I must re-login. Am I missing something or is this a
bug?
Ryan
Show replies by date
Just to follow up - looks like the distributable attribute is required in web.xml for
Wildfly session persistence to work. This was new to me since in GlassFish session
persistence worked without the distributable attribute being set in web.xml. I thought
this attribute was only for clusters, but apparently not as it is used in standalone mode
too.
________________________________
From: Ryan Slominski
Sent: Thursday, May 23, 2019 10:58 AM
To: keycloak-user
Subject: Wildfly Client Adapter breaks session persistence
It seems session persistence is broken with the Wildfly Client Adapter. I have:
<persistent-sessions/>
in the standalone.xml file under:
<servlet-container name="default">
This was set using the command:
.jboss-cli.sh --connect
--command="/subsystem=undertow/servlet-container=default/setting=persistent-sessions:add()"
However, if I run the command:
.jboss-cli.sh --connect --command="/deployment=myapp.war:redeploy()"
My authenticated session is lost and I must re-login. Am I missing something or is this a
bug?
Ryan