I followed the documentation to upgrade our EPiServer 7.5.1000.0 website to use 188.8.131.52. Got it all working, upgraded the database using the EPiUpdatePackage that we created, and all was fine.
Repeated the same steps in our seperate test servers, still ok.
Now with these changes deployed to production, when logging in using the EPiServer logon page we get 'logon failed' shown in red text above the textboxes, even when using correct credentials. The onyl difference in production is that the user accounts used are managed by SQLRoleProvider, whereas in test and development we use WindowsRoleProvider.
No errors seem to be generated in our logs, so unfortunately I cant provide any more details.
Output from the upgrade process:
Please could someone help?
As a clarification, it's "Login failed", not "Logon failed".
In the event log, we have the following:
Event code: 4007
Event message: URL authorization failed for the request.
Event time: 8/13/2014 3:34:57 PM
Event time (UTC): 8/13/2014 2:34:57 PM
Event ID: 2813ff5bfe2640e5ba9b76d07868aafc
Event sequence: 47
Event occurrence: 4
Event detail code: 0
Application domain: /LM/W3SVC/7/ROOT-1-130524131341220000
Trust level: Full
Application Virtual Path: /
Application Path: xxxxxxxxxxxxx
Machine name: xxxxxxxxxxxxx
Process ID: 3008
Process name: w3wp.exe
Account name: xxxxxxxxxxxx\AppUser_Epi75_DE_UAT
Request URL: http://xxxxxxxxxxx/episerver/cms
Request path: /episerver/cms
User host address: 127.0.0.1
Is authenticated: True
Authentication Type: Forms
Thread account name: xxxxxxxxxx\AppUser_Epi75_DE_UAT
I had some issues with authentication after an Commerce and EPi upgrade, two things, do u got following in your web.config?
If I remember correctly that hash algorithm is new for EPiServer 7.5, and I assume it should still be there in 7.11. Second thing I had issues with was that the cookie had expired of different reasons, so check so the timestamp of the cookie is still valid.
Resolved this - it was because we changed from SqlRoleProvider and SqlMembershipProvider to DefaultRoleProvider and DefaultMembershipProvider - changed this back for now.
Assuming that there should be some sort of migration process for data held in the SQL DB?