We are upgrading from Vaadin 8 to Vaadin 24. We also deployed Tomcat 10.
We are running Vaadin as a war on our Tomcat and using Apache2 as Reverse-Proxy.
When we click on logout, the redirect to /login is not working.
Snippet from config:
RewriteEngine On
RewriteRule “^/vaadin24/(.*)” “http://localhost:9080/vaadin24/$1” [P]
ProxyRequests off
- Vaadin / Flow version: 24.2.1
- Java version: openjdk 18.0.1.1
- OS version: Ubuntu 18.04.6 LTS
- Tomcat version: 10.1
- Apache2 version: Apache/2.4.29
So many questions… how do you logout the user… what does it redirect do and so on
I think logout process is not the issue. If I test with the embedded Tomcat, after logout I’ll be redirected to /login.
On the testing system with Apache it does not work to redirect to /login after logout.
Testing local with embedded Tomcat and on Tomcat & Apache differ.
Logout process:
drawer.add(new Button(“Logout”, e → authenticatedUser.logout()));
… goes to class AuthenticatedUser and authenticationContext.logout(); from package ‘com.vaadin.flow.spring.security’.
It might be possible that the logout() method does not check for the provided servlet context
Is there an option to check that?
You can check the source code in the flow repo. Best would probably to create an issue there with an reproducable example
It’s working now. Forgot ProxyPassreverse in proxy argh.