[MILAGRO-6] [Standalone D-TA] Abstract the D-TA Proxy Storage through an interface

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Component/s: Milagro Server
• Assignee: Unassigned
• Reporter: Simeon Aladjem
• Created: 06/Jun/16 14:36
• Updated: 01/Jun/19 12:18
• Resolved: 01/Jun/19 10:34

Description

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.

Issue Links

• depends upon: MILAGRO-4 [Standalone D-TA] Create an initial D-TA Proxy service
• is depended upon by: MILAGRO-9 [Standalone D-TA] Create a plain and simple implementation of D-TA Proxy Storage