[JBoss JIRA] Created: (JBPORTAL-2453) additional parameters for gadgets are lost when the gadgets are displayed
by Toshiya Kobayashi (JIRA)
additional parameters for gadgets are lost when the gadgets are displayed
-------------------------------------------------------------------------
Key: JBPORTAL-2453
URL: https://jira.jboss.org/jira/browse/JBPORTAL-2453
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Widget
Affects Versions: 2.7.2 Final, 2.7.0 Final, 2.7.1 Final
Reporter: Toshiya Kobayashi
Assignee: Magesh Kumar B
There are some gadgets which require additional parameters when you add the gadget to your dashboard.
For instance, these gadgets of Google Apps for hosted domain:
url=http://hosting.gmodules.com/ig/gadgets/file/117808631063490062819/hos...
url=http://hosting.gmodules.com/ig/gadgets/file/117808631063490062819/hos...
url=http://hosting.gmodules.com/ig/gadgets/file/117808631063490062819/hos...
But the values of the parameters which you have input will be lost when those gadgets are displayed.
## script tags that jboss-portal-2.7.2 generates ##
<script src="http://gmodules.com/ig/ifr?url=http://hosting.gmodules.com/ig/gadgets/fil..."></script>
<script src="http://gmodules.com/ig/ifr?url=http://hosting.gmodules.com/ig/gadgets/fil..."></script>
<script src="http://gmodules.com/ig/ifr?url=http://hosting.gmodules.com/ig/gadgets/fil..."></script>
## script tags that jboss-portal-2.6.6 generates ##
<script src="http://gmodules.com/ig/ifr?url=http://hosting.gmodules.com/ig/gadgets/fil..."></script>
<script src="http://gmodules.com/ig/ifr?url=http://hosting.gmodules.com/ig/gadgets/fil..."></script>
<script src="http://gmodules.com/ig/ifr?url=http://hosting.gmodules.com/ig/gadgets/fil..."></script>
Note: In order to reproduce it, first, you should fix org.jboss.portal.widget.google.provider.GGWidgetInfoBuilder in jboss-portal in the same way as JBEPP-109.
https://jira.jboss.org/jira/browse/JBEPP-109
If you want to reproduce it easily, use epp-4.3.0.GA CP02 to which JBEPP-109 has been already applyed.
As you see, script tags which jboss-portal-2.7.2 generates don't have parameters which you have input (e.g. up_Domain).
Those values seem to be stored in JBP_PORTAL_OBJECT_PROPS table.
Checked versions:
NG : 2.7.2, 2.7.1, 2.7.0, epp-4.3.0.GA CP02
OK : 2.6.8, 2.6.6
This problem seems to be introduced from 2.7.x
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBID-189) Add 'TokenElement' and 'TokenElementNS' to the SAML20TokenPovider in jboss-sts.xml
by Daniel Bevenius (JIRA)
Add 'TokenElement' and 'TokenElementNS' to the SAML20TokenPovider in jboss-sts.xml
----------------------------------------------------------------------------------
Key: JBID-189
URL: https://jira.jboss.org/jira/browse/JBID-189
Project: JBoss Identity
Issue Type: Task
Reporter: Daniel Bevenius
Assignee: Anil Saldhana
Priority: Minor
To get token validation to work using a saml assertion I needed to add the TokenElement and TokenElementNS to jboss-sts.xml:
<TokenProvider ProviderClass="org.jboss.identity.federation.core.wstrust.plugins.saml.SAML20TokenProvider"
TokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV2.0"
TokenElement="Assertion"
TokenElementNS="urn:oasis:names:tc:SAML:2.0:assertion"/>
Without this in jboss-sts.xml no provider will be found and a NullPointerException will be throw:
16:44:11,343 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
java.lang.NullPointerException
at org.jboss.identity.federation.core.wstrust.StandardRequestHandler.validate(StandardRequestHandler.java:336)
at org.jboss.identity.federation.bindings.jboss.wstrust.JBossSTS.handleTokenRequest(JBossSTS.java:142)
at org.jboss.identity.federation.bindings.jboss.wstrust.JBossSTS.invoke(JBossSTS.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Perhaps a check in StandardRequestHander that gives some more info would help:
if (provider == null)
throw new WSTrustException("No SecurityTokenProvider configured for " + securityToken.getNamespaceURI() + ":" + securityToken.getLocalName());
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBID-188) Update package name of SAML20TokenProvider in jboss-sts.xml
by Daniel Bevenius (JIRA)
Update package name of SAML20TokenProvider in jboss-sts.xml
-----------------------------------------------------------
Key: JBID-188
URL: https://jira.jboss.org/jira/browse/JBID-188
Project: JBoss Identity
Issue Type: Task
Reporter: Daniel Bevenius
Assignee: Anil Saldhana
Priority: Trivial
The current package name is:
<TokenProvider ProviderClass="org.jboss.identity.federation.api.wstrust.plugins.saml.SAML20TokenProvider"
I believe that the package name has changed to:
<TokenProvider ProviderClass="org.jboss.identity.federation.core.wstrust.plugins.saml.SAML20TokenProvider"
This can be found in jboss-identity-webapps/jboss-sts/src/resources/jboss-sts.xml. I was unsure about the Component to which this module belongs so I've left that option as 'Unknown'. Same goes for the versions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months