We are hitting a problem with Licenses and the enhanced authentication in Servoy 5.2. We converted our application to use enhanced authentication with separate Login and Authenticator solutions. Now when a user tries to login to our solution when the license limit for concurrent users has been reached Servoy shows our custom login window (with the splash window saying it is in demo mode) as I believe Servoy allows an extra license to the number purchased, but the Authenticator solution cannot access the server data to authenticate as I believe it requires a further license for a short period to authenticate.
An error is placed in the server log that “No more Licenses available”. However the problem is that the user trying to log in does not know this and they just get an authentication error suggesting they have entered the wrong password.
We also hit the same problem when a Headless Client is triggered on an external event. If all the licenses are used then the Headless Client logs into the Login solution (with the “extra” license) but then cannot authenticate (requiring a further extra license) and it then hangs in the Login solution without carrying out its function, and it does not close itself down.
Have we implented something wrongly, or is this expected behaviour? If it is expected we would rather the user is given the message that there are no licenses left when they try to login (before being asked to enter their password), and the headless client is prevented from starting when there are no licenses left, rather than hanging in the Login solution.
Discovered this the hard way some weeks ago. Very annoying…
I guess every (temp) license counts for Servoy ?
Can you really do that much in an authenticator module so that a license is required (in Servoy opinion) ?
Its not just the feedback to the user that causes the problem but the Headless Client getting stuck in the Login solution when it is started. I’ll raise a case and try to cover both things.
We saw this also!, we have a client with 5 licenses.
When 4 are logged in, number 5 want’s to login, and starts in the login solution, (which is license number 5)
the login solution, starts the authenticator, which is number 6!! and the sh…t hits the fan…
so +1 for not consuming a license for the authenticator…
Or make it the other way around! Don’t consume a license for the login-solution! You can’t do ANYTHING in the login-solution, except talking/validating against the authenticator
In my opinion licenses should not be consumed for both the login and the authenticator solutions.
Think about webclient, sometimes people hit your login page and then navigate away, sometimes robots do that. It’s quite easy to run out of licenses in this scenario.
Yes, can this also be done for the login solution? As I explained before if you deploy webclient as part of a website (let’s say a customer area) it’s quite easy that visitors hit you login page consuming a license and then navigate away.
ngervasi:
Yes, can this also be done for the login solution? As I explained before if you deploy webclient as part of a website (let’s say a customer area) it’s quite easy that visitors hit you login page consuming a license and then navigate away.
Nicola,
A end-user-client will always consume a license, even before login.
An authenticator client is different because it always runs on-behalf-of another client so that other client consumes the license.