[
https://issues.apache.org/jira/browse/CXF-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Pasierb updated CXF-6359:
-----------------------------
Attachment: 0001-NPE-fix.patch
Moving {{keyManagers}} variable initialization using
{{SSLUtils.getDefaultKeyStoreManagers(LOG)}} before the logic that checks if
{{certAlias}} is set seems to fix this.
I don't know CXF that well so please verify if the patch is acceptable.
The patch also includes a few tests showing the problem.
> NullPointerException when certAlias specified but no keyManagers are
> configured
> -------------------------------------------------------------------------------
>
> Key: CXF-6359
> URL: https://issues.apache.org/jira/browse/CXF-6359
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.7.15
> Reporter: Tom Pasierb
> Priority: Minor
> Attachments: 0001-NPE-fix.patch
>
>
> When only {{certAlias}} is specified in {{tlsClientParameters}} with no
> keyManagers a {{NullPointerException}} is thrown regardless the keystore is
> specified using {{javax.net.ssl.keyStore}} system property or not.
> In a use case I have I want my client to be able to specify a {{certAlias}}
> in configuration file but this is expected to be used only when the server
> actually requires client certificate and a keystore with the given alias is
> specified using {{javax.net.ssl.keyStore}} system property.
> I'd like to specify tlsClientParameters like:
> {code:xml}
> <http:tlsClientParameters disableCNCheck="${disableCNCheck}">
> <sec:certAlias>${certAlias}</sec:certAlias>
> </http:tlsClientParameters>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
