First Party Authentication for REST Fails with 401 / Unauthorized in WLS But Works In Standalone (Doc ID 2699448.1)

Last updated on AUGUST 07, 2024

Applies to:

Oracle REST Data Services - Version 3.0.12 and later
Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.

Goal

Authentication for ORDS REST services has been set up according to one of the following for ORDS standalone:

<Note 2305632.1> - Oracle REST Data Services Demo - Authentication (First Party)
https://oracle-base.com/articles/misc/oracle-rest-data-services-ords-authentication#first-party-authentication

For example:
curl -i -k --user <USERNAME>:<PASSWORD> http://<HOSTNAME>:<PORT>/ords/ordsexample/testmodule/emp/7788

where <USERNAME>:<PASSWORD> are the user and password. Please note <> are not part of the syntax.

However, when testing with ORDS deployed on WebLogic, the same request fails with a 401 authentication error:
curl -i -k --user <USERNAME>:<PASSWORD> http://<WLS_HOSTNAME>:<PORT>/ords/ordsexample/testmodule/emp/7788
HTTP/1.1 401 Unauthorized

NOTE: The example(s) provided are for demonstration purposes only and represents fictitious data. Any similarity to actual data, web sites and / or persons, living or dead, is purely coincidental and not intended in any manner.

Why is the WLS request failing?

Solution

	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

Goal

Solution

References

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

First Party Authentication for REST Fails with 401 / Unauthorized in WLS But Works In Standalone (Doc ID 2699448.1)

Applies to:

Goal

Solution

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

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