You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Scott Wilson (Created) (JIRA)" <ji...@apache.org> on 2012/03/23 16:31:29 UTC
[jira] [Created] (WOOKIE-331) Move API Keys from the database into
a configuration file
Move API Keys from the database into a configuration file
---------------------------------------------------------
Key: WOOKIE-331
URL: https://issues.apache.org/jira/browse/WOOKIE-331
Project: Wookie
Issue Type: Improvement
Components: Server
Reporter: Scott Wilson
Fix For: 0.10.0
As we remove the Admin UI its less easy to manage API keys if your only option is the REST API; there are also no actual DB relationships between API keys and the rest of the data model. For these reasons I'm proposing to change the storage of API keys to a configuration text file, e.g.
#
# Scott's API key for testing
#
bananas = scottbw@apache.org
This file could then be edited directly by the server admin to make changes if they don't want to manage the server through the REST API.
As with policies it means existing implementations have to migrate from the DB to the text file, but this should be trivial.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (WOOKIE-331) Move API Keys from the database into
a configuration file
Posted by "Scott Wilson (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Wilson reassigned WOOKIE-331:
-----------------------------------
Assignee: Scott Wilson
> Move API Keys from the database into a configuration file
> ---------------------------------------------------------
>
> Key: WOOKIE-331
> URL: https://issues.apache.org/jira/browse/WOOKIE-331
> Project: Wookie
> Issue Type: Improvement
> Components: Server
> Reporter: Scott Wilson
> Assignee: Scott Wilson
> Fix For: 0.10.0
>
>
> As we remove the Admin UI its less easy to manage API keys if your only option is the REST API; there are also no actual DB relationships between API keys and the rest of the data model. For these reasons I'm proposing to change the storage of API keys to a configuration text file, e.g.
> #
> # Scott's API key for testing
> #
> bananas = scottbw@apache.org
> This file could then be edited directly by the server admin to make changes if they don't want to manage the server through the REST API.
> As with policies it means existing implementations have to migrate from the DB to the text file, but this should be trivial.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira