[JBoss JIRA] Created: (GTNPORTAL-1052) configuration of oauth for signed request
by jerem j (JIRA)
configuration of oauth for signed request
-----------------------------------------
Key: GTNPORTAL-1052
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1052
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0-GA
Reporter: jerem j
In gadget, you can do request to an oAuth endpoint.
In some case, the distant server want to make sure who is the server (or developer) doing the request. To do so, they provide a oauth consumer key and a oauth consumer secret. You need to associate this with your gadget. So everytime your gadget is going to do request to their server, it will use this keys.
For example, google is using such a mechanism to protect their analytics APIs. You need to register a domain on https://www.google.com/accounts/ManageDomains and google will give you the OAuth Consumer Key and OAuth Consumer Secret.
The problem is that to configure this now, you need to modify the file oauth.json that is located in jar.
It's something similar to what has been done for http://jira.exoplatform.org/browse/SOC-650 but the properties are different:
* Gadget URL
* oAuth endpoint name (used in the gadget to reference this endpoint)
* consumer_key
* consumer_secret
* key_type
Also a UI to configure this would be awesome.
--
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
11 years, 9 months
[JBoss JIRA] Created: (GTNPORTAL-985) Many users can not add pages at once during Perf test
by Arthur Peltier (JIRA)
Many users can not add pages at once during Perf test
-----------------------------------------------------
Key: GTNPORTAL-985
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-985
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0-GA
Environment: IE7, FF3.5 - JBoss 5.1.0.GA- Java1.6.0-14
Reporter: Arthur Peltier
Steps:
- Create group and assign user to that group
- Create page by winzard
Scenarios:
- Run with 2 threads with the scripts with steps above by Jmeter
Result:
- 2 groups are created <-- it is ok
- Only 1 page is created <--- it is invalid.
The problem may be conflict of concurrence. Because when I run 1 user but with repeat actions( steps by steps), many pages are created successfully. However, when many users are run at once, only 1 page is created.
Expected :
- Able to add many pages at once with many v-users.
--
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
11 years, 9 months
[JBoss JIRA] Created: (GTNWSRP-16) Visibility of remote portlets in App.registry
by Michal Vanco (JIRA)
Visibility of remote portlets in App.registry
---------------------------------------------
Key: GTNWSRP-16
URL: https://jira.jboss.org/jira/browse/GTNWSRP-16
Project: GateIn WSRP
Issue Type: Bug
Components: Admin GUI
Affects Versions: 1.0.0
Reporter: Michal Vanco
Assignee: Chris Laprun
When I create new consumer, I can see remote portlet in App.registry
(Portlets/Remote), when I click Auto Import, category with remote
portlet is created.
When I deactivate consumer, I can't see the portlet in App.category
(Portlets/Remote), but when I click Auto import, category with remote
portlet is still there. Is it ok? Shouldn't it dissapper if it is not
present?
I am also able to add this remote portlet to page and it works.
After I delete consumer, I can still see the caterory with portlet in
App.registry, when click Auto import, in log is:
ERROR [STDERR] org.gatein.pc.api.NoSuchPortletException: No such portlet
self./jboss-image-portlet-sample-remotable-GateIn.jboss-image-portlet-sample
And when I add this portlet to page I can see
"This portlet encountered an error and could not be displayed"
and in log is:
org.gatein.pc.api.NoSuchPortletException: No such portlet self./jboss-image-portlet-sample-remotable-GateIn.jboss-image-portlet-sample
I think that when I deactivate/delete consumer, I shouldn't be able to see its portlets anywhere.
--
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
11 years, 9 months
[JBoss JIRA] Created: (GTNPORTAL-1123) portal skins shouldn't need to include screenshots of the other skins
by Matt Wringe (JIRA)
portal skins shouldn't need to include screenshots of the other skins
---------------------------------------------------------------------
Key: GTNPORTAL-1123
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1123
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Matt Wringe
When you switch portal skins you can be shown a preview screenshot of the portal skin to see which one you want to select.
The problem is that for this preview to be shown the current portal skin must contain the image of all the other skins as part of its own css. In order for this to work currently it means when a new skin is created, someone needs to go through all the other skins to add the new skin screenshot image and reference for the new skin. It doesn't make any sense for a portal skin to have references to other skins screenshots.
A portal skin should specify the preview screenshot itself, and the skin switcher should use this to show the screenshot.
[ps: it might also be good to show an image not found image rather than just leave the preview area blank]
--
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
11 years, 9 months
[JBoss JIRA] Created: (GTNPORTAL-961) No limits on the MapResourceBundle recursive lookup
by Matt Wringe (JIRA)
No limits on the MapResourceBundle recursive lookup
---------------------------------------------------
Key: GTNPORTAL-961
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-961
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Matt Wringe
The map resource bundle doesn't have any limits on the amount of recursion it will try and do when resolving a message.
For example, if we have a properties file with:
word.cancel=#{word.cancel}
Then we will end up in an infinite loop (eventual stackoverflow exception) when trying to resolve #{word.cancel}.
When it tries to resolve word.cancel, it will get back #{word.cancel} which it will try and resolve again, ...
We are going to need to have a check on the level of recursion allowed when resolving messages from the resource bundle.
--
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
11 years, 9 months
[JBoss JIRA] Created: (GTNPORTAL-933) Remove custom_*.* resource bundles from portal.war
by Patrice Lamarque (JIRA)
Remove custom_*.* resource bundles from portal.war
--------------------------------------------------
Key: GTNPORTAL-933
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-933
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0-GA
Reporter: Patrice Lamarque
Priority: Minor
custom_* resource bundles are provided inside portal.war and contain a single entry (test=test).
I guess that the intention of this file, like for Portal 2.5, is to provide an out-of the box extension point for custom i18n keys.
for the record, in portal 2.x we used to override these bundle files at build time, effectively modifying these files in the portal.war.
With GateIn's portal extension mechanism, I expect (maybe erroneously) to be able to add custom locales simply by putting some custom_*.properties files inside my own portal war (ex: csdemo.war!WEB-INF/classes/locale/custom.properties ). And rely on the classloader resolution provided by the extension mecanism.
Strangely, it works well for all but english (en)locale.
The keys of my custom.properties are not resolved in my own gtmpl.
For example, in my homepage's gtmpl, an expression such as <%=_ctx.appRes("UIHomePagePortlet.cs-community")%> will result in displaying the "cs-community" which means the key was not resolved.
I have several workarounds possible :
1. copy-paste ALL custom*.* in my own portal war (ex: csdemo.war!WEB-INF/classes/locale/) then modify the bundles for the translations I have
2. digg into the ResourceBundleService xml conf change the "portal.resource.names" to add something like "locale.portal.csdemo" for my own keys
3. remove portal.war!WEB-INF/classes/locale/custom*.* and only provide the bundles for the locales I want (ex: custom.properties)
1. is not pratically doable (I can't guess how many languages are supported
2. is the current workaround. But then you could very well remove custom*.*
3. is almost good except the need to modify portal.war in order to obtain the expected behaviour
I'm not sure if this could qualify as a but, but none of the possible solutions is satifying in terms of extensibility.
The quickfix for gatein would be simply to remove custom*.* from portal.war. By keeping the ResourceBundleService config as-is, it would make a very handy implicit extension point for customizations.
--
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
11 years, 9 months