Connector Rule - Leverage Additional JAR

A web services endpoint we’re connecting to has a custom authentication scheme. It requires us to add a header with an RSA encrypted string of the request body + a few additional attributes. I wanted to evaluate if that was something realistic to accomplish in a Web Service Before Create rule. If we’re able to reference additional JARs this seems doable, otherwise, it might require a custom connector.

I was told from another person you can take this approach:

You can create custom source with custom type using webservices connector, where in source you can have upload option, upload option will enable you to upload 3rd party required jar for running rule, then you can configure before create rule to use classes from uploaded jar.