Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 794468 - (JBEPP-1508) Gadgets which are not whitelisted in the proxy should provide a notification
Gadgets which are not whitelisted in the proxy should provide a notification
Status: VERIFIED
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal (Show other bugs)
unspecified
Unspecified Unspecified
high Severity high
: ER04
: 6.2.0
Assigned To: Juraci Paixão Kröhling
vramik
http://jira.jboss.org/jira/browse/JBE...
:
Depends On:
Blocks: 1072147
  Show dependency treegraph
 
Reported: 2012-02-09 10:38 EST by Matt Wringe
Modified: 2018-02-06 14:18 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Previously, if a gadget tried to use a proxy URL which was not whitelisted, the gadget would silently fail. In many cases, a log message was not recorded for the failure. This could have resulted in customers incorrectly assuming the gadget contained a bug instead of the actual reason of the gadget using an unauthorized proxy connection. The enhancement introduces an INFO level log entry describing the root cause of the failure.
Story Points: ---
Clone Of:
: 1072147 (view as bug list)
Environment:
Last Closed:
Type: Feature Request
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker GTNPORTAL-3363 Major Resolved Provide feedback on logs when gadget is not white-listed 2018-01-31 13:24 EST
JBoss Issue Tracker JBEPP-1508 Major Closed Gadgets which are not whitelisted in the proxy should provide a notification 2018-01-31 13:24 EST

  None (edit)
Description Matt Wringe 2012-02-09 10:38:56 EST
project_key: JBEPP

Currently if a gadget tries to use a proxy url which is not whitelisted, the gadget will just silently fail.

This means that a gadget may not display anything on the portal page, and there may not be any message in the logs about this. Without a notification it gives the impression that gadgets are currently broken rather than the gadget is using an unauthorized proxy connection.

For example, this portlet when used on a page in the gadget wrapper portlet: http://hosting.gmodules.com/ig/gadgets/file/112581010116074801021/hamster.xml
Comment 2 Boleslaw Dawidowicz 2014-01-09 05:37:13 EST
We should try to have *at least* some meaningful info in the logs as currently it fails silently.
Comment 3 Juraci Paixão Kröhling 2014-01-10 12:12:50 EST
Pull request: https://github.com/gatein/gatein-portal/pull/760
Comment 4 Peter Palaga 2014-01-15 10:56:33 EST
Fixed in GateIn master.
Comment 6 Peter Palaga 2014-06-21 06:44:56 EDT
This must have been fixed in JBoss Portal 6.2.0 DR1 already, but the Target Milestone field was unset till now.

Note You need to log in before you can comment on or make changes to this bug.