Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Future consideration
Workspace App Connect
Created by Guest
Created on Nov 13, 2024

RELATED IDEAS

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.

Idea priority High
  • Admin
    Ben Thompson
    Reply
    |     Nov 25, 2024

    Thank you for taking the time to raise this request, which we agree would bring additional value. Supporting different non-standard forms of authentication brings with it challenges due to the many different possible variations in the way that the tokens are transmitted are exposed, so what might work well for Veeva, may not be applicable to other use cases. With that said, we approve of the concept regardless, so we are promoting the idea to status of Future Consideration. FYI @Varun Jain

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.