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 (Updated) (JIRA)" <ji...@apache.org> on 2012/03/28 23:57:34 UTC

[jira] [Updated] (WOOKIE-214) Support API key migration

     [ https://issues.apache.org/jira/browse/WOOKIE-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Wilson updated WOOKIE-214:
--------------------------------

    Attachment: key_migration_patch.txt

Patch for this attached - however I think its worth exploring the model of changing the authn solution to remove the need for this fix rather than apply it (see also MAC proposal from Tien)
                
> Support API key migration
> -------------------------
>
>                 Key: WOOKIE-214
>                 URL: https://issues.apache.org/jira/browse/WOOKIE-214
>             Project: Wookie
>          Issue Type: New Feature
>          Components: Server
>            Reporter: Scott Wilson
>         Attachments: key_migration_patch.txt
>
>
> We should support the case of enabling an administrator to migrate an API key - for example, to exchange a compromised key for a reissued key without causing any problems for existing Widget Instances and any data associated with them. This should be exposed using the PUT method of the API Key REST API.

--
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