Version 10 to Version 11 Upgrade problem at login screen

[tmerrill]

I�m new to Alpha 5 and am picking up a web application that is working but needs a lot of additional work. Before I became involved someone upgraded from version 10 to version 11. Both versions are running on a server, and according to the information I have, they are configured correctly (webroot 10 and webroot 11) and we should be able to have both running at the same time. They are accessing a MySQL database.
I went through the security tutorials, and I believe that Alpha security has been used to build the login page and the logic behind it. It appears to be a fairly standard login process, again from looking at the tutorial.
If I enter a valid username and password on the version 10 login screen I am correctly taken to the next screen the application. If I enter an invalid username/password I get the appropriate error message on the login screen.
If I enter a valid username and password on the version 11 screen, it flashes and returns me to the login screen, with no entries in either the username or password fields. Interestingly, if I enter an invalid username/password I get the appropriate error message on the login screen. So, it must be checking correctly, but somehow can�t put up the next screen when the check is correct.
If I shut version 10 down I still can't login to version 11 - it behaves exactly the same.
Has anyone else run into this problem when upgrading? I�m not sure how to debug this. Any help would be greatly appreciated.

[iRadiate]

Re: Version 10 to Version 11 Upgrade problem at login screen

Todd,

Sounds like a permissions problem to me.
Go into your v11 Web Projects Control Panel and check your web security configuration, particularly redirect page after login.
Also, I'd check your page security settings to make sure the redirect page is set properly.
If you make any changes republish your security.

Stephen

[Pat Bremkamp]

Re: Version 10 to Version 11 Upgrade problem at login screen

Sounds like a session variable problem. There could be a routine in the page the page you are going to that checks to see if a session variable exists or has a certain value, and if not, it returns to the login screen. Depending on what it is checking, it could easily work in V10, but not in V11.

[tmerrill]

Re: Version 10 to Version 11 Upgrade problem at login screen

Stephen, thanks for the reply. It looks like the web security configuration is the same as v10, as well as the page security settings. I saw this in the release notes:

"Session variables can only be strings. Other variable types are not supported and my not work as expected."

I found a module called SetSessionVars that contains this

' create session vars
dim e as p
dim session.admin as l = .f.
dim session.companyid as n = 0
dim session.inspectorid as n = 0
dim session.associationid as n = 0
dim session.reportuid as n = 0
dim session.componentuid as n = 0
dim session.reportid as n = 0
dim session.usergroup as c
session.usergroup = session.__protected__pGroup

Do you think these all need to be redefined as strings? And then of course anything downstream would also need to be changed.

[tmerrill]

Re: Version 10 to Version 11 Upgrade problem at login screen

Thanks Pat. I wondered about that. I don't know if you saw my reply to Stephen earlier. But here it is for you.

I saw this in the release notes:

"Session variables can only be strings. Other variable types are not supported and my not work as expected."

I found a module called SetSessionVars that contains this

' create session vars
dim e as p
dim session.admin as l = .f.
dim session.companyid as n = 0
dim session.inspectorid as n = 0
dim session.associationid as n = 0
dim session.reportuid as n = 0
dim session.componentuid as n = 0
dim session.reportid as n = 0
dim session.usergroup as c
session.usergroup = session.__protected__pGroup

Do you think these all need to be redefined as strings? And then of course anything downstream would also need to be changed.