My Oracle Support Banner

Call to Webservices/Rest/Provider/isActive/ With Valid Username and Password Returns Could Not Authenticate User / Token or HTTP/1.1 401 Unauthorized and AuthType is TOKEN (Doc ID 3060044.1)

Last updated on NOVEMBER 20, 2024

Applies to:

Oracle E-Business Suite Integrated SOA Gateway - Version 12.2.9 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.9 version, Installation Issues

IsActive should work with username or token but only works with token.

When calling /webservices/rest/provider/isActive/ in a web browser and providing a valid username and password combination

or when repeating the call with curl and a valid credentials the following errors are observed:
 

On a web browser: could not authenticate user / token

As the output of curl command line: HTTP/1.1 401 Unauthorized

In both cases, ISGLog.log shows: 
Auth type value from fnd_soa_service_policies is for classId : 4617 and derivedId : 5132 is : TOKEN


The issue can be reproduced at will with the following steps:

1. Call in a web browser: /webservices/rest/provider/isActive/

2. Enter valid username and password when prompted and notice the error: could not authenticate user / token

2.1 The same can be tested with curl:

 

This shows a call to isActive with valid username fails and a call to login with valid username works and returns a token which can then be successfully used with isActive.

IsActive should work with both username or token but only works with token.

Changes

 

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!


In this Document
Symptoms
Changes
Cause
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.