1 of 1 people found this helpful
You can't do this easily and not without compromising security in some sense.
In order to use your own login screen and attempts-checking you already have to inside your solution and scripts need to run. Some people will reply to say that you can use an auto-login account with limited privileges so that you can take the user through your layouts and scripts and use the ReLogin script step. But that has proven time and time again to be a huge risk that usually leads to the file being vulnerable to being compromised. Scripts can be stopped, the auto-login account will in essence let anyone into the file - even for the briefest of moments and in that moment things can happen.
If you are not happy with the tools that FM gives you to authenticate users, then look at using external authentication instead and leverage the tools available in Active Directory, Open Directory and local accounts/groups in the OS of the FMS box.
ok Windecorte, I'm sure you're absolutely right, about security issues.
I suppose the security breach could happen during the data flow from the login windows to the ReLogin script step, because we cannot use a simple couple of variables, but we need to temporary write username/password couple into a local table and then use them with ReLogin script step, isn't it ?
There's other possible security breaches but yes: you'll be using the data structures to pass security info, which is never good.
Thank you Windecorte: that's what I suspected.
Honestly I'm not in trouble with Filemaker authentication/authorization BACKEND (inside FM, local-OS, Directory ...): obviously the problem is the FRONTEND (user interface) that is not user customisable with graphics and other useful information to be passed to the FIRST application layout (language, data-set in a multi-company environment ...).
I'm afraid it's not easy or even possible to find a solution with the current level of Filemaker technology.
Thank you again.