ms3inc / camel-rest-extensions Goto Github PK

    @Bean
    public SSLContextParameters builtin() throws GeneralSecurityException {
        TrustManagerFactory managerFactory = TrustManagerFactory
                .getInstance(TrustManagerFactory.getDefaultAlgorithm());
        managerFactory.init((KeyStore) null);

        TrustManagersParameters trustParams = new TrustManagersParameters();
        trustParams.setTrustManager(managerFactory.getTrustManagers()[0]);

        SSLContextParameters answer = new SSLContextParameters();
        answer.setTrustManagers(trustParams);

        return answer;
    }

    @Bean
    public UndertowComponent client(SSLContextParameters builtin) {
        UndertowComponent answer = new UndertowComponent();
        answer.setSslContextParameters(builtin);

        return answer;
    }

see:
https://access.redhat.com/documentation/en-us/red_hat_amq/6.3/html/security_guide/ssl-sysprops
https://gist.github.com/ravishankarhassain/51ccfbdb350f7ee57a05799655ccd94a
https://camel.apache.org/manual/latest/camel-configuration-utilities.html
https://stackoverflow.com/questions/19005318/implementing-x509trustmanager-passing-on-part-of-the-verification-to-existing/19005844#19005844
https://stackoverflow.com/questions/24555890/using-a-custom-truststore-in-java-as-well-as-the-default-one
https://stackoverflow.com/questions/31920719/getting-the-trusted-x509certificate-for-a-java-sslsocket
https://github.com/square/okhttp/blob/okhttp_4.9.x/okhttp/src/main/kotlin/okhttp3/internal/platform/Platform.kt

Currently the validators only validate with contentType.equals("application/xml") and contentType.equals("application/json"). Need to add multipart request support and investigate what multipart support the swagger-request-validator has.

The following may be helpful for the OpenApi4J validation:

• https://www.openapi4j.org/operation-validator.html#supported-body-content-types
• https://github.com/openapi4j/openapi4j/blob/master/openapi-operation-validator/src/main/java/org/openapi4j/operation/validator/util/convert/MultipartConverter.java

Using the archetype with camel-rest-extensions, when migrating APIs where the specification paths cannot be changed, this path pattern collision issue sometimes occurs. There may be other bugs but this seems to be the most common one.

Since openapi4j is archived, it means there's no support for fixing bugs like this.

Alternative libraries:

• com.atlassian.oai swagger-request-validator-core is already part of this project and according to this camel-rest-extensions merged PR it was switched from because it didn't offer XML support, and there is still an open issue for XML support with the validator
• ?