Hi,
I've been using the oidc-client since it was introduced and it has worked great. With wildfly 36 however I've got a new behavior that does not happen in 35.
I have a Vaadin application that has web.xml configured with
<login-config>
<auth-method>OIDC</auth-method>
</login-config>
I've always configured the oidc.json file like this when container is deployed
cat << EOF > /opt/bitnami/wildfly/stage/oidc.json
{
"client-id": "${OIDC_CLIENT_ID}",
"provider-url": "${OIDC_PROVIDER_URL}",
"ssl-required": "${OIDC_SSL_REQ}",
"public-client": ${OIDC_PUBLIC_CLIENT},
${TRUST_MANAGER_SNIPPET}
"confidential-port": 443
}
EOF
This has always worked great, and does in wildfly 35. With wildfly 36, I can log in to my application just fine and if I continue to click around everything works fine. However, if I stop on a particular screen for greater than 60s to read an email, whatever, the next click on something sends it back to the app's home screen(like my token timed out) but it doesn't make me login again, meaning the keycloak token is still valid.
I was particularly interested in wildfly 36 to see if this issue I had opened had been resolved
https://issues.redhat.com/browse/ELY-2753I don't see any exceptions in the logs when this happens, I just see a message that acts as if I had logged in again
Any thoughts?