Not sure if this is a Servoy issue or related to our production Debian Linux environment (which is a standard serovy 5.2.15 install and has nginx to proxy requests back to servoy).
The solution is set to mustAuthenticate and has a loginForm specified.
If a webclient user successfully logs in, then inadvertently hits the browser’s ‘back’ arrow they get to the login form - no surprises there.
From that point, it’s impossible to get to the logged in state again, neither by filling out the login form and clicking the login button to run our Submit method, nor by clicking the forward arrow. The client is alive in the Servoy Admin panel and we can send messages to the client. Logging shows that the Submit method is running correctly.
Can anyone tell me if this behaviour is just the way it is with the Servoy security? If not, I’ll dig deeper before submitting a support case.
Ho Scott, The problem you describe occurs after 3 successful logins. This looks like a different problem, it happens when the client is already logged in, and returns to the loginForm. From there it’s impossible to get to the solution. It’s still present in 5.2.15
this will not be in the next 5.2.x release because that one is already build and in testing.
Also backporting is not always that easy because of a lot of dependencies. So you could create a case to see if this one can be backported without needing to get a lot more.
The quickest way is to upgrade to 6.1.x when we release 6.1.4