[jira] [Closed] (MILAGRO-6) [Standalone D-TA] Abstract the D-TA Proxy Storage through an interface

["Brian Spector (JIRA)" <ji...@apache.org>]

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

Brian Spector closed MILAGRO-6.
-------------------------------
    Resolution: Not A Problem

> [Standalone D-TA] Abstract the D-TA Proxy Storage through an interface
> ----------------------------------------------------------------------
>
>                 Key: MILAGRO-6
>                 URL: https://issues.apache.org/jira/browse/MILAGRO-6
>             Project: Milagro
>          Issue Type: Task
>          Components: Standalone D-TA
>            Reporter: Simeon Aladjem
>            Priority: Major
>
> As mentioned in MILAGRO-4, the D-TA Proxy might have a storage that would list:
> * Relying Party Applications (_RPA_) ID's and Keys (AppId/AppKey)
> * Client Keys generation events (per RPA)
> * Time Permits generation events (per RPA)
> Having such a storage might enable efficient request signature verification (see MILAGRO-5), which might be based on the AppKey.
> The storage might be updated by a separate service that would register RPA's, generate AppID's and AppKeys for them and add them to the storage.
> The storage itself is implementation specific and might vary and therefor needs to be abstracted.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)