Bug 794468 (JBEPP-1508) - Gadgets which are not whitelisted in the proxy should provide a notification
Summary: Gadgets which are not whitelisted in the proxy should provide a notification
Keywords:
Status: VERIFIED
Alias: JBEPP-1508
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER04
: 6.2.0
Assignee: Nobody
QA Contact: vramik
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks: 1072147
TreeView+ depends on / blocked
 
Reported: 2012-02-09 15:38 UTC by Matt Wringe
Modified: 2021-11-14 22:29 UTC (History)
6 users (show)

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.
Clone Of:
: 1072147 (view as bug list)
Environment:
Last Closed:
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker GTNPORTAL-3363 0 Major Resolved Provide feedback on logs when gadget is not white-listed 2020-07-15 23:27:08 UTC
Red Hat Issue Tracker JBEPP-1508 0 Major Closed Gadgets which are not whitelisted in the proxy should provide a notification 2020-07-15 23:27:07 UTC

Description Matt Wringe 2012-02-09 15:38:56 UTC
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 10:37:13 UTC
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 17:12:50 UTC
Pull request: https://github.com/gatein/gatein-portal/pull/760

Comment 4 Peter Palaga 2014-01-15 15:56:33 UTC
Fixed in GateIn master.

Comment 6 Peter Palaga 2014-06-21 10:44:56 UTC
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.