[
https://issues.apache.org/jira/browse/SLING-13280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18114772#comment-18114772
]
Konrad Windszus commented on SLING-13280:
-----------------------------------------
Fixed in
[https://github.com/apache/sling-org-apache-sling-commons-crypto/commit/5431d49bfbbe1ba3954bf32edbf4b4d078edc025].
This also automatically registers all SecurityProviders (detected via
{{META-INF/services/java.security.Provider}} resource) as OSGi service and via
[Security.addProvider(Provider)|https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/security/Security.html#addProvider(java.security.Provider)].
In addition it exposes a WebConsole plugin at
{{sling-commons-crypto-jca-provider-algorithms}} exposing all algorithms
provided by all registered providers.
> Provide a CryptoService implementation just relying on JCA
> ----------------------------------------------------------
>
> Key: SLING-13280
> URL: https://issues.apache.org/jira/browse/SLING-13280
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Commons Crypto 1.3.0
>
>
> As the only other implementation
> https://github.com/apache/sling-org-apache-sling-commons-crypto/blob/dea1d738623fa01ca78a5fd839007b4c489b6c20/src/main/java/org/apache/sling/commons/crypto/jasypt/internal/JasyptStandardPbeStringCryptoService.java
> is relying on the meanwhile no longer maintained library jasypt an
> alternative should be provided.
> Compare with the discussion at
> https://lists.apache.org/thread/qsnbfvyyt1qh3826qpsywzhzqkkxfl6p
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
