Enable OAuth 2.0 Security Profile Support on HTTP Request Nodes

Currently, the REST Request node in App Connect Enterprise supports OAuth 2.0 authentication natively via Security Profiles. This is an excellent feature that allows for a "configuration-over-code" approach to handling token acquisition and lifecycle management.

The Gap:

The standard HTTP Request node lacks this native integration. To achieve the same OAuth 2.0 connectivity on an HTTP node, developers are forced to write custom ESQL/Java or create separate sub-flows to manually handle the handshake, token caching, and refreshing.

Solution:

Please extend the Security Profile capabilities of the HTTP Request node to fully support OAuth 2.0, matching the feature set currently available in the REST Request node.

Advantages:

Development Efficiency: Eliminates the need to write and test complex custom ESQL or Java code just to manage OAuth token lifecycles (fetching, caching, and refreshing).

Standardization: Aligns the HTTP Request node with the REST Request node, offering a consistent "configuration-first" experience across different protocol nodes.

Better Reliability: Native platform handling of token expiration and refresh loops is significantly less error-prone than custom, developer-written logic.

Simplified Maintenance: Moves security details out of the flow logic and into Policies/Profiles. If security credentials change, the operational team can update the Policy without developers needing to redeploy the BAR file.