-
Type:
Defect
-
Resolution: Won't Do
-
Priority:
Major
-
Affects Version/s: 1.2.0-BETA1
-
Component/s: Authorization
-
None
I had created a test user "admin_test" on my Gateway instance (1.2-BETA). I logged in with this user using Google Chrome. I then installed 1.2-BETA2, cleared the database and sesame store ready for a fresh install. When I visited the site with the same browser session the Gateway administrator received 10s of emails reporting "AuthenticationCredentialsNotFoundException: Cannot find user with username=admin_test".
The app initially appeared fine from the browser but started reporting internal server errors later on.
I am assuming this is caused by persistent cookie data since I tried hard to remove all state from the previous Gateway install.
The app initially appeared fine from the browser but started reporting internal server errors later on.
I am assuming this is caused by persistent cookie data since I tried hard to remove all state from the previous Gateway install.