| Summary: | Logged to Riftsaw console as not authenticated | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Ivo Bek <ibek> |
| Component: | riftsaw | Assignee: | Jeff Yu <cyu> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.2.0dev2 | CC: | gary.pi4tech, kconner, mbaluch |
| Target Milestone: | --- | ||
| Target Release: | 5.2.0 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-3181 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-08 00:55:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Ivo Bek
2011-07-18 10:10:28 UTC
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 |