[
https://issues.apache.org/jira/browse/MILAGRO-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simeon Aladjem updated MILAGRO-4:
---------------------------------
Description:
The D-TA Proxy exists in order to prevent direct access to the D-TA itself.
* The D-TA Proxy should be written in Golang in order to utilize this
technology's strengths
* The functionality of the D-TA Proxy is:
** To receive the requests for keys generation or time permits and verify
that hey were made by a valid source
** Potentially to update a database with the events of generating Client
Keys and Time Permits
was:
The D-TA Proxy exists in order to prevent direct access to the D-TA itself.
The functionality of the D-TA Proxy is:
* To receive the requests for keys generation or time permits and verify that
hey were made by a valid source
* Potentially to update a database with the events of generating Client Keys
and Time Permits
> [Standalone D-TA] Create an initial D-TA Proxy service
> -------------------------------------------------------
>
> Key: MILAGRO-4
> URL: https://issues.apache.org/jira/browse/MILAGRO-4
> Project: Milagro
> Issue Type: Task
> Components: Standalone D-TA
> Reporter: Simeon Aladjem
>
> The D-TA Proxy exists in order to prevent direct access to the D-TA itself.
> * The D-TA Proxy should be written in Golang in order to utilize this
> technology's strengths
> * The functionality of the D-TA Proxy is:
> ** To receive the requests for keys generation or time permits and verify
> that hey were made by a valid source
> ** Potentially to update a database with the events of generating Client
> Keys and Time Permits
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
