You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@rave.apache.org by "Jasha Joachimsthal (JIRA)" <ji...@apache.org> on 2011/08/24 18:02:29 UTC

[jira] [Commented] (RAVE-84) Oauth key and secrets need to be maintainable (and secure)

    [ https://issues.apache.org/jira/browse/RAVE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090314#comment-13090314 ] 

Jasha Joachimsthal commented on RAVE-84:
----------------------------------------

http://incubator.apache.org/rave/documentation/oauth-consumer.html

> Oauth key and secrets need to be maintainable (and secure)
> ----------------------------------------------------------
>
>                 Key: RAVE-84
>                 URL: https://issues.apache.org/jira/browse/RAVE-84
>             Project: Rave
>          Issue Type: Sub-task
>          Components: build & development
>            Reporter: Okke Harsta
>            Assignee: Okke Harsta
>             Fix For: 0.3-INCUBATING
>
>
> The keys & secrets for OAuth are in Shindig out-of-the-box located in a json file. We need to store them somewhere (e.g. in the database) in order to add key secrets without having to restart the application. Also - but that is not part of this issue - we need an interface to maintain the key/secrets.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira