Bug 476669
Summary: | Shared child channels look really bad in Overveiw-> Org Trust view | ||||||
---|---|---|---|---|---|---|---|
Product: | [Community] Spacewalk | Reporter: | wes hayutin <whayutin> | ||||
Component: | WebUI | Assignee: | Jesus M. Rodriguez <jesusr> | ||||
Status: | CLOSED WONTFIX | QA Contact: | wes hayutin <whayutin> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 0.4 | CC: | duffy, jesusr | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
URL: | https://dhcp231-223.rdu.redhat.com/rhn/multiorg/channels/Consumed.do?oid=62 | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-03-11 02:22:31 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 456553 | ||||||
Attachments: |
|
Description
wes hayutin
2008-12-16 15:09:57 UTC
Created attachment 327113 [details]
ss
this would be a global change to all the channel lists and estimating about 6 hours effort. moving this to low priority since current functionality works and this is a question of appearance. the one downside to this request is it does create a data leakage for the parent channel name. probably not a big security concern but worth mentioning since a parent name could have release/version info in the name that should not be shared out. Moving to space05. Like shughes said, this is not a localized issue and requires a more broad view of the UI. Adding mizmo on the Cc and NEEDINFO for a proposed better way. I'm ok with putting in the name followed by (no access). But usually the reason we don't list the name is you don't have access to it so you don't get to see anything about it, including the name. I don't think putting the name is a good idea because there may be information in the name that is not public. (E.g., think of the ISP Satellite usecase: the parent channel name might have the name of another customer on the Satellite. This kind of information leakage is bad.) The channel can't be consumed if you can't access its parent can it? Child channels can... be consumed even if the org does NOT have rights to the parent. created that scenario on the latest build If we can't show the user the base channel name, there is really no other thing to show other than 'no access to parent' which is pretty much self explanatory. I'm going to close this as WONTFIX. Jesus, you can't say WHY there is no access? eg "<em>Parent channel inaccessible. Insufficient entitlements. For access, contact your organization administrator</em>" "<em>Parent channel inaccessible. Insufficient permissions. For access, contact your organization administrator.</em>" Explain the problem clearly and give some pointers as to how to fix it. |