[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
12 years, 7 months
[JBoss JIRA] Created: (GTNPORTAL-1376) NewPortalConfigListener should allow for overwriting of default values
by Matt Wringe (JIRA)
NewPortalConfigListener should allow for overwriting of default values
----------------------------------------------------------------------
Key: GTNPORTAL-1376
URL: https://jira.jboss.org/browse/GTNPORTAL-1376
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Matt Wringe
When creating a new portal, the NewPortalConfigListener merges the configurations between the old portal and new one, because of this we end up with duplicate configuration entries which can cause issues. See NewPortalConfigListener.mergePlugin
What should be happening, is if the new portal sets a configuration option which the default portal also has set, then we should just use the value set in the new portal.
An example of this can be seen in the sample portal, the sample portal specified to only use root as a predefinedOwner, but its picking up the other users specified in the default portal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months