[
https://issues.apache.org/jira/browse/SLING-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888730#comment-17888730
]
Oliver Lietz commented on SLING-12450:
--------------------------------------
[~rombert], The class names were changed from to {{*PBE*}} to {{*Pbe*}} between
1.0.0 and 1.1.0 with commitÂ
[e7cad7181edd3bacd85ed240d03a3700f75df6d1|https://github.com/apache/sling-org-apache-sling-commons-crypto/commit/e7cad7181edd3bacd85ed240d03a3700f75df6d1].
> Commons Crypto sample and documentation reference incorrect Factory PID
> -----------------------------------------------------------------------
>
> Key: SLING-12450
> URL: https://issues.apache.org/jira/browse/SLING-12450
> Project: Sling
> Issue Type: Bug
> Components: Commons, Documentation
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
>
> https://sling.apache.org/documentation/bundles/commons-crypto.html as well as
> https://github.com/apache/sling-samples/blob/master/sling-commons-crypto-configuration/src/main/resources/initial-content/apps/samples/commons-crypto/config/org.apache.sling.commons.crypto.jasypt.internal.JasyptStandardPBEStringCryptoService~sample.json
> use and incorrect config name that translate into an incorrect factory PID
> The "PBE" part is actually "Pbe" in the OSGi component definitions, see
> https://github.com/apache/sling-org-apache-sling-commons-crypto/blob/607fed7f5db7fce08ffd24b9cd39bec3c1966d39/src/main/java/org/apache/sling/commons/crypto/jasypt/internal/JasyptStandardPbeStringCryptoService.java#L60
> .
> I noticed this while defining the config in the feature model, but I suspect
> the OSGi installer will have the same issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
