[ 
https://issues.apache.org/jira/browse/CAMEL-18973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681553#comment-17681553
 ] 

Claus Ibsen commented on CAMEL-18973:
-------------------------------------

Okay so its how certifictes are loaded in camel - as in 3.20 we now load using 
a standard way in Camel, that loads from classpath by default. And you want to 
load from file system, so it should be like

{code}
  ssl:
    server:
      trust-self-signed: true
      certificate:
        path: "file:src/test/resources/keystore.p12"
        password: "changeit"
        type: "PKCS12"
    client:
      certificate:
        path: "file:src/test/resources/keystore-mtls.p12"
        password: "changeit"
        type: "PKCS12"
{code}

eg with file: as prefix

This was also documented in the 3.19 -> 3.20 upgrade guide
https://camel.apache.org/manual/camel-3x-upgrade-guide-3_20.html#_camel_api



> camel http - mTLS not working anymore
> -------------------------------------
>
>                 Key: CAMEL-18973
>                 URL: https://issues.apache.org/jira/browse/CAMEL-18973
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-http
>    Affects Versions: 3.20.1
>            Reporter: Alex Landini
>            Priority: Major
>
> Hi,
> I'm trying to update apache camel version from version 3.18.4 to version 
> 3.20.1.
> I have an integration with a rest api exposed through https with mtls 
> authentication.
> I created a SSLContextParameters object with the keystores configuration .
> With apache camel 3.18.4 everything is working fine starting from 3.20.1 
> stopped working,
> if I removed the mtls from the server everything works fine, I'm getting the 
> following error from the server:
> Caused by: javax.net.ssl.SSLException: readHandshakeRecord
>  
> I created a test case with wiremock to simulate the external API, you can 
> check the following repository with a full example:
> [https://github.com/landal79/camel-mtls-test]
>  
> Thanks



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to