Link: Added: This issue depends RIFTSAW-399

Jeff, I tried reproducing this with 5.2DEV2, but was unable to log in with either admin/admin or admin/password login details. So not sure what is different in SOA-P to riftsaw - the only different is DEV2 still has 2.2.6.Final of the console.

As pointed out by Doug, the user details need to be uncommented in server/default/conf/props/soa-users.properties - once this was done, the admin/admin username password details worked fine, so could not reproduce the issue reported by Ivo.

Hi Gary, does the console support a guest account?. In my experience you will not be able to login if soa-users.properties doesn't contain uncommented user details.

Hi Marek - no guest account. I was not aware of the soa-users.properties file in SOA-P before, but seems to work fine when this line is uncommented. So until the line is uncommented the user would not be able to access the console - which I guess is as planned, to make sure the user explicitly sets up valid username/passwords.

Yes that's exactly my point. user:password pairs must be set up to access the console. How is it possible to login as "Not authenticated"?

Not sure - will need to wait for Jeff to return from PTO next week to investigate further. I have been unable to reproduce, so can't be sure.

Candidate, not committed for 5.2

Temporarily reopening for release note status.

Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage