Support OAuth 2.0 Authentication for RosettaNet PIP Transport (HTTPS)

Business Context

Global electronics and semiconductor supply chains are increasingly adopting stricter security standards for B2B integrations. Token-based authentication mechanisms such as OAuth 2.0 are becoming mandatory, even for established industry standards like RosettaNet.

In particular, NVIDIA, as a leading semiconductor and AI platform provider, now requires OAuth 2.0–based authentication for RosettaNet message exchanges instead of traditional HTTPS basic or certificate-based authentication.

Current Limitation

The current IBM webMethods RosettaNet module supports RosettaNet PIP message exchange over HTTPS using basic authentication or certificate-based security only.
As confirmed by IBM webMethods support, OAuth 2.0 authentication is not supported for either inbound or outbound RosettaNet message transport.

Due to this limitation, customers cannot comply with partner-mandated security policies without implementing non-standard custom solutions outside the RosettaNet framework.

Customer & Market Impact

When major trading partners such as NVIDIA enforce OAuth 2.0 as a mandatory security standard, existing RosettaNet integrations are no longer sufficient without additional custom development or external proxy components.

This limitation:

• Creates a blocker for new partner onboarding
• Increases operational and maintenance complexity
• Undermines the use of RosettaNet as a standardized, out-of-the-box B2B solution in semiconductor and high-tech industries

Requested Enhancement

We request IBM webMethods to enhance the RosettaNet module to support OAuth 2.0 authentication at the transport layer, including:

• OAuth 2.0 client credentials flow for outbound RosettaNet PIP messages
• OAuth token validation for inbound RosettaNet messages
• Configuration and lifecycle management within webMethods (Integration Server / Trading Networks / RosettaNet module), without requiring custom wrappers