ORDS OAuth Token Generation Fails With Authentication/Authorization Errors with WLS in SSL (Doc ID 2400211.1)

Last updated on NOVEMBER 11, 2022

Applies to:

Symptoms

ORDS has been configured and tested with OAuth2 in standalone mode successfully according to the documentation:
https://docs.oracle.com/database/ords-17/AELIG/developing-REST-applications.htm#AELIG3000

After deploying ORDS in WLS / SSL, ORDS REST requests work in general, but when configured for OAuth,

Authorization errors are occurring when trying to generate the OAuth token:

* In below command replace <WLS_HOST>:<WLS_PORT> with the real values without  the <>

curl -i -k --user <Client_ID..><Client_Secret..> --data "grant_type=client_credentials" https://<WLS_HOST>:<WLS_PORT>/ords/schema/oauth/token
HTTP/1.1 401 Unauthorized
Date: Tue, 15 May 2018 19:21:06 GMT
Content-Length: 1468
Content-Type: text/html; charset=UTF-8
WWW-Authenticate: Basic realm="weblogic"

Error 401--Unauthorized

The version of ORDS tested was 17.3.4, however, this error occurs in other versions, as well.

Changes

OAuth authentication is being configured for ORDS deployed in a Weblogic server running in SSL.
ORDS requests without OAuth authentication run successfully in this environment.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.