[gatein-issues] [JBoss JIRA] Updated: (GTNPORTAL-1052) configuration of oauth for signed request

[Khoi Nguyen (JIRA)]

     [ https://jira.jboss.org/browse/GTNPORTAL-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Khoi Nguyen updated GTNPORTAL-1052:
-----------------------------------

    Labels: portal-s43  (was: )


> configuration of oauth for signed request
> -----------------------------------------
>
>                 Key: GTNPORTAL-1052
>                 URL: https://jira.jboss.org/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
>              Labels: portal-s43
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira