So, in updating an old project with Wappler 2 years ago I just want to create a new login with Security Provider.
I did this in the last project before 4.4.5 and 4.5.0.
But the Docs show something from 2019 & the Security providers, as far as I can tell, have changed.
What’s weird still is that the 3 field username, password, remember me login form mentioned in the old docs does not yet have a stock block or component Wappler template for precisely that. The Documents section describes setting it up manually.
At any rate, here is where I am – My login query will find the unique User credentials for these 2 fields from the Login Post values. But what am I to do with the Permissions Tab “Permission Name” , “Table”, “Identity Column” and “Conditions” settings?
I can’t select anything, I can’t type into them. And since I’ve already specified the only 3 conditions needed : table used for checking authorized users, Identity, Username & Password – Why are these other settings needed?
I’d expect that this would already look like “Permission Name Identity from table cobraloginvalidate equals apo_Kunden_ID” or some such thing.
So, please, Where is the updated Login Page with Security Provider step-by-step Document?
This login page does redirect to the correct form but now I want to set up the security provider & the Success and Unauthorized/Try Again with the updated Wappler components.
All you need to do is add your Permission Name, select the table which contains the authentication data, , ie userRegistration/userPermissions etc, then select the column which is used as the identity, id, uid, etc.
In the Conditions panel pick (double click) a column from which you store your user group, for example, then its operator, usually equal to, and finally the value, which could be anything from a numeric to alphanumeric value used as a cross reference, again an example.
So would be:
group = adminXYZ
landing = adminXYZ
There has been very little change to this for a long time so the documentation should relate just fine.
I think you are mixing the process of creating a login step and defining your global security provider. It’s really pretty simple.
Under globals you define a security provider, one for the whole site. You define it only there, under Globals > Security Providers. Here you just select your users table, the unique ID column for this table and the columns containing the usernames and passwords for your users, i.e. the details they enter later in the login form to log in:
You don’t NEED to add permissions if you don’t use permissions for your users. That is not mandatory.
Then you go, create Server Action under API and add the Login step there. Note - just a single login step, nothing else, you don’t add the security provider step in the server actions any longer. There you define the login step.
You create your login server connect form on the page and select the login action for it.
Then is my “loginvalidate” API looking correct so far where I am also setting a cookie?
And is this setting ONE cookie with both variables or have I mistakenly set TWO cookies for each variable?
