You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2021/01/14 15:24:00 UTC

[jira] [Resolved] (SLING-7821) Switch code signing to use the SAS CSP for Java Hash Signing

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

Robert Munteanu resolved SLING-7821.
------------------------------------
    Fix Version/s:     (was: Sling Eclipse IDE 1.2.4)
       Resolution: Won't Fix

That variant is no longer valid, see https://infra.apache.org/digicert-access.html .

> Switch code signing to use the SAS CSP for Java Hash Signing
> ------------------------------------------------------------
>
>                 Key: SLING-7821
>                 URL: https://issues.apache.org/jira/browse/SLING-7821
>             Project: Sling
>          Issue Type: Task
>          Components: IDE
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Major
>
> There is a simpler way of signing the IDE tooling code offline, see https://docs.digicert.com/api-developer-portal/secure-app-service-api/downloads-and-resources/sas-csp-for-java-hash-signing/ . The documentation also references the possibility of executing the process using the {{maven-jarsigner-plugin}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)