djlapin wrote:Hi Paul,
I commented out that line, and the error went away. Thank you for pointing out that the user doesn't need to exist.
I'm mystified that the user doesn't have to exist first, and also that the error never occurred in the previous version (6.0.
. If security.login() doesn't verify against some sort of internal password mechanism, then why can't we bypass the internal mechanism entirely, for the user to get into the program?
Thank you
Don
Paul?
Don,
Security.login() is meant for when you have your own login check (like what Harjo does) and when the user/password validates against that, the security.login() call just informs Servoy that the current user is logged in.
In case of authenticator solutions, this is then propagated to the calling client.
Users in Servoy Security are only needed if you let Servoy do the password checking, for example when your solution has mustAuthenticate=true and you do not have a login form or login solution.
Note that the groups you pass in security.login() do have to exist because these are used in permissions checking on forms and tables.
Rob