I have done further testing... the findings were more than a little surprising. To eliminate as many variables as possible I did the following:
Create a entirely new BSV - from blank, added only 1 process with the following rule - DISPLAY MESSAGE 'test', nothing else was added to the bsv. I set that process to the forgotten password process and published the bsv.
To make sure there was not a form issue I by-passed the form entirely by going directly to the LogonFP.aw?<newbsv>
Testing in this manner had the following results:
safari - fires the process 2 times on the aware server, it sets 2 sessions in safari. Cookies are 43 bytes.
firefox - fires the process 8 times on the aware server, it sets 8 sessions in safari. Cookies are 183 bytes.
chrome - fires the process once. Cookie is 223 bytes.
Ie - fires the process once. Cookie is 183 bytes.
I then logged into my Admin console to confirm how many process were running - for fun I watched fiddler - it logged me in 8 times!!! So then I decided to try my main app - yup 8 times. I then went to the smaple apps hosted by Aware... same result. So, I suspect there is an issue with how a session is set when they url has parameters.
Would anyone else mind doing the same to confirm? Just fire up fiddler, open firefox (with Fiddler add-in enabled), then log into your app.
