custhelp.com

Create or use an Oracle B2C Service staff account and enable the needed API permissions on its profile. For SOAP, enable Public SOAP API under Configuration > Staff Management > Profiles > Permissions > Administration as described in Connect Web Services for SOAP access. Oracle recommends creating a dedicated account for API use. REST session auth can also use an agent account to mint a session token via AgentAuthenticator() as shown in Session authentication for REST API.

Obtain a session token from the Agent Browser UI Extensibility Framework IExtensionGlobalContext.getSessionToken, or generate it with a custom PHP script that calls AgentAuthenticator::authenticateCredentials(...) and returns session_id, as shown in Session authentication for REST API. This token is then sent as Authorization: Session <token>.

Configure an external identity provider for the site under Single Sign-On Configurations > OAUTH, upload the public certificate, and create or use an agent account with SSO Login (SAML 2.0) enabled. Then generate an RS256 JWT matching the documented claims (sub, iss, exp, jti, aud) as described in Element Manager Public API authentication.

First generate an Element Manager public API token by calling POST /api/elementmanager/authentication/authToken with a JWT bearer token and interfaceUrl header, as described in Element Manager Public API authentication. Use the returned token to call Element Manager public REST endpoints.

Use an Oracle B2C Service user account that can access Chat APIs, then send WS-Security UsernameToken credentials in the SOAP header together with a client AppID in the ClientRequestHeader, as shown in Simple example of how to authenticate to the Chat UQ API.