Bug 1168661
| Summary: | Teiid user (role user) can't switch to another workspace in Dashboard | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Virtualization 6 | Reporter: | Filip Elias <felias> |
| Component: | Dashboard Builder | Assignee: | Van Halbert <vhalbert> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | David Le Sage <dlesage> |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | atangrin, vhalbert |
| Target Milestone: | ER5 | Keywords: | QA-Closed |
| Target Release: | 6.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The Teiid user (role user) could not switch to another workspace in Dashboard. When Database Logging is enabled, this is problematic as the default workspace is SecurityLogging and the user cannot switch to the showcase workspace to see the examples. To control who has access to audit and command logging, a role called logging has been created that the user must have.
|
Story Points: | --- |
| Clone Of: | Environment: |
DV 6.1 ER4
|
|
| Last Closed: | 2016-02-10 08:53:18 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: | |
| Embargoed: | |||
|
Description
Filip Elias
2014-11-27 14:27:14 UTC
To control who has access to audit and command logging, a role called logging, has been created that the user must have. OOTB: a) "user" role can see the showcase (sample) workspace. b) "admin" role can see and configure all workspaces c) "logging"role can see logging workspace and the showcase workspace. Van Halbert <vhalbert> updated the status of jira TEIIDDSHB-9 to Resolved Just a note on this issue. The ability to switch from one workspace to another is up to the dashboard builder designer. The designer must enable this capability. This isn't an internal dashboard builder function that either works or it doesn't. But to show that it can be enabled, the OOTB dashboard has it enabled for the 2 workspaces that are provided. But that doesn't guarantee if another workspace is added it will be enabled. Van Halbert <vhalbert> updated the status of jira TEIIDDSHB-9 to Closed |