Bug 794468 (JBEPP-1508)

Summary:	Gadgets which are not whitelisted in the proxy should provide a notification
Product:	[JBoss] JBoss Enterprise Portal Platform 6	Reporter:	Matt Wringe <mwringe>
Component:	Portal	Assignee:	Nobody <nobody>
Status:	VERIFIED ---	QA Contact:	vramik
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	bdawidow, epp-bugs, jpallich, ppalaga, theute, vramik
Target Milestone:	ER04
Target Release:	6.2.0
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEPP-1508
Whiteboard:
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:
Clones:	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:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1072147

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.

Comment 7 vramik 2014-07-03 14:18:28 UTC

Verified in ER04. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EPP/view/EPP/view/6.2/view/UI%20Other/job/epp6_ui_selenium_tests_RFE_BZ794468/14/