My Oracle Support Banner

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

Last updated on MAY 17, 2018

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.

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:
curl -i -k --user MhxTQwQmmQAxqlXit_Zwmw..:E98XeCW3eLSpHpyKsUGrlg.. --data "grant_type=client_credentials" https://managedserver:8002/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

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


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