oltu-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Tripodi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OLTU-166) Extract signature APIs in a separate package
Date Mon, 08 Dec 2014 19:15:13 GMT

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

Simone Tripodi updated OLTU-166:
--------------------------------
    Attachment: OLTU-166.patch

Please see attached patch for the initial version of signature module

> Extract signature APIs in a separate package
> --------------------------------------------
>
>                 Key: OLTU-166
>                 URL: https://issues.apache.org/jira/browse/OLTU-166
>             Project: Apache Oltu
>          Issue Type: RTC
>            Reporter: Simone Tripodi
>            Assignee: Simone Tripodi
>         Attachments: OLTU-166.patch
>
>
> As reported in dev@ ML,
> due to OLTU-165 I thought that [signature APIs|http://svn.apache.org/repos/asf/oltu/trunk/jose/jws/src/main/java/org/apache/oltu/jose/jws/signature/]
in JWS are subject of interest also for consumers which do not require the whole JWS, I mean
that they could be extracted and released in a separated module under our [commons|http://svn.apache.org/repos/asf/oltu/trunk/commons/]
components, then
>  * future major versions of JWS can depend to the signature module;
>  * future modules that will require signature, don't have to reimplement algorithms/depend
on JWS
> WDYT?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message