Servoy Forum

I have a couple clients that get close to their license limits because of users sitting on the login page. Users logout, timeout, etc and end up sitting on the login page consuming a license. I'm aware of work-round that could kill their session and redirect them to a different page, but this doesn't feel like a good user experience. Users should be able to sit on the login page indefinitely without consuming a license.
Login solutions have very limited feature sets since they can't directly access the datasources, so there is little chance of this being abused.

Servoy team, can we make this change in a future release?

I've created a jira case for this at: https://support.servoy.com/browse/SVY-15433 and included a poll in this post.

Totally agree! +1

+1

Also voted on the Jira ticket

totally agree,

we discussed already in 2011

viewtopic.php?f=3&t=15921&hilit=login+license#p85866

Harjo wrote:totally agree,

we discussed already in 2011

viewtopic.php?f=3&t=15921&hilit=login+license#p85866

Seems like that just stopped consuming licenses for Authenticators. We need it to stop consuming licenses for users just sitting in the Login Solution.

goldcougar wrote:Seems like that just stopped consuming licenses for Authenticators. We need it to stop consuming licenses for users just sitting in the Login Solution.

In NG you don't even need authenticator/login solution.
Looking from that perspective, more generic this could be 'unauthenticated sessions should not be consuming licenses'.
But how to deal with solutions that don't require authentication?

mboegem wrote:In NG you don't even need authenticator/login solution.
Looking from that perspective, more generic this could be 'unauthenticated sessions should not be consuming licenses'.
But how to deal with solutions that don't require authentication?

Right, that would complicate things though, since you could build solutions without authentication and get the full power of Servoy without licenses. So, my proposal keeps it simple. Just don't count licenses on login solutions. Then, even for NG, people can implement login solutions that need to take advantage of not counting licenses for those users. Since login solutions are locked down without direct data access, it seems like a reasonable request.

+1

+1 (annoying for 10+ years).

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.

can you build in or fix this than, and bind such property/feature to only 1 form??n the login form?

We are looking into the case created by gold cougar.
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 ?

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.