Hi kotinkarwak,
I think you can safely comment out the 2 lines for fields.USERID.value=fields.PARAM1.value and fields.PASSWORD.value=fields.PARAM2.value;
Thanks for the comprehensive screencast. I think I know what the problem is. I am going to assume that you have at least a basic understanding of SQL.
In most of my database resources, I usually use Native SQL because I find it to be a lot more flexible although it does require a little bit more work than assisted SQL the reward is that with a good understanding of SQL you can create in more complex and powerful SQL statements.
Now having said that, if you click on native SQL in your USERS database resource for a moment, you will see that 4 tabs appear for the SELECT,UPDATE,INSERT and DELETE SQL statements where you would write the 4 statements that correspond to each (SELECT,UPDATE,INSERT and DELETE).
The SELECT statement in my native SQL database resource looks like this:
In this case, I build the where clause of the SELECT statement myself. However, you are using Assisted SQL so that doesn't really apply and wont work.
Personally, I recommend native or assisted SQL but this can be fixed in one of 2 ways depending on which one you choose for this database resource.
If you want to continue using assisted SQL change the line:
tables.USERS.WHERECLAUSE.value=.... <im>
to these 2 lines: (And by the way, in my case, I convert the username to lowercase so that the username doesn't have to be case sensitive but that's not required. It's up to you. If you want the username to be case sensitive change LOWER(tables.USERS.USERNAME.value) to tables.USERS.USERNAME.value and change fields.PARAM1_VALUE.value.toLowerCase() to fields.PARAM1_VALUE.value)
LOWER(tables.USERS.USERNAME.value)=fields.PARAM1_VALUE.value.toLowerCase();
tables.USERS.PASSWORD.value=fields.PARAM2_VALUE;
If you do decide to use native SQL for this database resource, the WHERE clause that you already have should work fine.
Please let me know if this works. If not, please add more print statements to trace the execution like you already did to figure out where its messing up
Also,
In LOGIN_REQUEST, under the events tab you reference both LOGON_SERVICE_JS and LOGON_SERVICE_LOGIC (which is the FPL login script). You do not need both and this will most like cause issues. Please remove LOGON_SERVICE_LOGIC from the events tab.
Segi