jcompagner wrote:Problem with this is that i rather have that people stop using login solutions..
Thats really not needed and over complicates things in Servoy (or in the solution)
Just use a login form...
As an example, if you have a login solution that doesn't have a soluton title text set but the main solution has one.. Then that is a big performance penalty because we need to constantly clone the whole login solution...
(so always set a login title text!)
But really, just stop using them, it over complicates things and is really only needed for the smart client.
But then this problem described in this post can't be fixed by this solution.
I would be fine to stop using them, but still need a fix so users on the login page don't count toward licensing
sean wrote:We are looking into the case created by goldcougar.
However, we would have to be careful that we don't create loopholes which could be abused.
Also, I wonder if this can just be solved with an idle timeout which redirects to a non-servoy client page ?
Agreed about the loophole, thats why I was hoping the use of loginSolutions would cover this, but as you mentioned on the ticket, loginSolutions aren't sandboxed in non-smart clients.
Can it be solved with an idle timeout which redirects to a non-servoy client page? That is really bad UX, and given Servoy's push about providing great user experiences, its really going in the wrong direction. Most apps don't do this, and the only reason it would be needed is because of how Servoy handles licenses. There are also situations where it doesn't work at all. I have a client with offices spread around the world, and during shift changes, users logout or timeout, while other users are trying to get into the system to start their shift. So this creates a bottleneck on the licensing. Yes, there are workarounds to this, but the default way Servoy handles it should promote providing good UX. Currently it doesn't.