Enhance the Connector Development Kit to support non-standard mechanisms of HTTP authentication

My team has been attempting to build connectors for reusable functions pertaining to the Veeva Vault suite of products. These APIs unfortunately do not adhere to strict HTTP authentication specs, like Basic Auth or OAuth, but their authentication mechanism is relatively straightforward when using API development utilities like Postman. There is an authentication endpoint to call when passing a username and password, and if authentication is successful, the system sends back an auth token in the body. This token then used as the value of the Authorization header in each subsequent request. While non-standard, even a simple copy/paste pattern for authentication tokens into headers of the HTTP request would go a long way towards enabling connections into systems that are "close" to following the HTTP Authentication specification, but not quite all the way there.

Veeva Vault is a critical, business-facing system within my organization, and App Connect lacking the ability to natively integrate with it is impacting our enterprise-wide adoption of App Connect.

Additional Details:

• Steps to duplicate this issue:

  • Create a flow using App Connect Designer

  • Get a session_id in the body of the response message by making the first invocation to Veeva Vault.

  • During the next invocation, pass that session_id as a HTTP header parameter to perform the next action successfully.