ORDS OAuth Token Generation Fails With Authentication/Authorization Errors with WLS in SSL
(Doc ID 2400211.1)
Last updated on JUNE 21, 2021
Applies to:Oracle REST Data Services - Version 17.4.1 and later
Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
ORDS has been configured and tested with OAuth2 in standalone mode successfully according to the documentation:
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-Type: text/html; charset=UTF-8
WWW-Authenticate: Basic realm="weblogic"
The version of ORDS tested was 17.3.4, however, this error occurs in other versions, as well.
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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document