[
https://issues.apache.org/jira/browse/SLING-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-13340.
-------------------------------------
Resolution: Fixed
Fixed in
https://github.com/apache/sling-org-apache-sling-commons-crypto/commit/d2eba75b1fc8177de9a5eeba9cd1e2cde2670d04.
> Do no longer use java.security.Provider OSGi service in
> JasyptStandardPbeStringCryptoService
> --------------------------------------------------------------------------------------------
>
> Key: SLING-13340
> URL: https://issues.apache.org/jira/browse/SLING-13340
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Affects Versions: Commons Crypto 1.2.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Commons Crypto 1.3.0
>
>
> The JasyptStandardPbeStringCryptoService optionally used an OSGi service of
> type {{java.security.Provider}}. Next to it it also allowed to use a custom
> (already registered provider) via OSGi configuration property
> {{securityProviderName}}. With SLING-13280 all bundles coming with a
> {{META-INF/services/java.security.Provider}} resource are automatically
> registered as OSGi service java.security.Provider making them used preferably.
> Therefore the eager binding of OSGi service {{java.security.Provider}} should
> be removed from {{JasyptStandardPbeStringCryptoService}}. To still rely on on
> custom providers use OSGi configuration property {{securityProviderName}} and
> rely on the automatic registration of custom providers added in the context
> of SLING-13280.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
