Skip Navigation

Search

Deprecation of Basic Authentication for Public APIs
Answer ID 13139   |   Last Review Date 05/08/2026

Environment

Oracle B2C Service Connect Web Services

Overview

Oracle B2C Service is announcing the deprecation of Basic Authentication for accessing public APIs. Due to increasing security risks associated with password-based authentication mechanisms, Basic Authentication will no longer be supported in a future release.

Customers currently using Basic Authentication must migrate to supported token-based authentication methods such as OAuth 2.0, SAML, or CX Session authentication.

Reason for Deprecation

To enhance platform security, Oracle is discontinuing support for Basic Authentication across public APIs.

Basic Authentication relies on usernames and passwords that may become stale, reused, exposed, or otherwise compromised over time. Continued use of password-based authentication presents a significant security risk that Oracle has determined is too risky to continue supporting.\

Modern token-based authentication methods provide stronger security controls, including:

  • Token expiration and renewal 
  • Reduced credential exposure 
  • Improved access governance 
  • Enhanced auditing and traceability 
  • Better protection against credential compromise 

Adopting OAuth2, SAML, or CX Session authentication ensures that only current, valid authentication tokens are used when accessing public APIs.

Deprecated Items

The following services will no longer support Basic Authentication:

  • Connect Web Services for REST (all variants) 
  • Connect Web Services for SOAP 
  • Connect Web Services for Knowledge 
  • Connect Web Services for Chat

Any integrations, scripts, middleware, applications, or custom implementations using Basic Authentication with these services must be updated.