Adding two Authentication behaviours..?

I have a page (index.asp) that requires two forms to authenticate users to two different sections.

i added the first one (ClubStore log in) and all is well, but when I add the second login (FA Store log in) i run into issues.

the first problem i get is with both behaviours named "WA_AuthParameter1.Add", so i've changed the second set to "WA_AuthParameter2.Add" and all worked fine. (i have done this with three forms on a prevoious page and all log in ok)

the first login (Clubstore) form works fine and authenticates but the second one wont work. i either get an error in line 19 of the HelperVB saying application uses wrong type, or, if i experiment with the form triggers in both log in's it just refuses to authenticate the second form (FaLogin)

i have tried setting both log in form triffers to "any form button pressed" or specified the eact trigger for each, but neither gets a result.

all files are attached but it says the "max file upload is 293k" (?) so i cant send the dBase. i can confirm as a "for instance" that the correct login details for "Birmingham FA" are CLubID = 130 and Password = "password"

- any clues?

and what is the procedure when i want more than login form on a page - have i done the right thing by running the authentication behaviour twice and then renaming all instances of WA_AuthParameter1.Add etc, to WA_AuthParameter2.Add

thanks in advance for your help as always


Russell

Based on the way that you have both of these setup it seems like it should work. Do you only get the error with the second authentication on the same page? What happens for you if the second authenticate server behavior is added to a page by itself with the login form for it? I think this would be a good test to determine if it is the fact that it is on the same page that is the problem or if there is something else about that authenticate server behavior that has problems.

As for setting up the login page properly it should not be necessary to have two different login forms with two different authentication server behaviors if both of server behaviors are interacting with the same table.

Please explain a little about why you are trying it this way, there may be an easier simpler solution for you.

ok, i'll do some experimenting.

all i'm trying to do is to have a section for club members to log in and go to their club page, and to have a similar (but maybe not identical) log in for FA Members to log in and go to the FA store page.

Both are using data from the same table "tblClubs". I've double-checked the settings but the second (FA) login always shows as "incorrect login"


I'll do more testing as per our seugestion - thanks Eric

I think you could do this with a single login. You would login the user then redirect them to the higher level access page. On this page you should have an access restriction rule for the higher access level users. You should have the redirect go to the lesser access level page. On the lesser access level page you would have a check for being logged in, the redirect for this should take the user to the login page.

If you set it up like this all users can use the same login page, when they login they will go to the higher access level page. If they have access they will stay on this page. If they have the lesser access level they will be redirected to the lesser access level page.

This should get you past the need to have two different logins going to different pages.