My Oracle Support Banner

FailedAuthentication Error For XML Request in a Cluster Configuration (Doc ID 1306248.1)

Last updated on MAY 23, 2019

Applies to:

Oracle Utilities Framework - Version 2.2.0.0.0 and later
Information in this document applies to any platform.

Goal

**Examples provided in this article do not represent real life personal/confidential information**

**Disclaimer:** This KM article may include the following abbreviations:

OUAF/FW - Oracle Utilities Framework
WSDL - Web Services Description Language
XAI - XML Application Integration
SOA - Service Oriented Architecture
SOAP - Simple Object Access Protocol
URL - Uniform Resource Locator
XML - eXtensible Markup Language

The XAI inbound service works on a default installation on Weblogic. When the cm.*.templates are used to convert a default install to a "cluster" configuration (ie: separate Admin Server and Managed Server and define a Weblogic cluster on custom ports), then the XAI Inbound Service no longer works. Accessing one XAI Inbound Service in SOAP UI via managed server will result in SOAP response fault wsse:FailedAuthentication although the user has been created and granted right access rights.

The following error shows in the logs:

- 2011-02-22 16:50:54,538 [[ACTIVE] ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] ERROR (xai.servlet.XAIWSServlet) Invalid user name or password
java.lang.Exception: Invalid user name or password
at com.splwg.xai.servlet.XAIWSServlet.doPost(XAIWSServlet.java:82)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

Setting XAI Option "Enforce SOAP Authentication = N" in a cluster configuration allows the XML request to succeed, however, this is not the desired approach to be used.

The WSDL for all the services is visible by accessing the URL in a browser. However, it is noticed that the namespace in the WSDL uses the server URL.

Replication Steps:
Cluster:
Admin server and managed server are separated.
Create a user and grant correct access rights.
The WDSL can be accessed.
Testing via SOAP fails with the following error:

<soap:Envelope xmlns:soap="http://<NAME>.xmlsoap.org/soap/envelope/"
xmlns:wsse="http://<NAME>.org/2001/XMLSchema-instance">
<soap:Header/>
<soap:Body>
<soap:Fault>
<faultcode>wsse:FailedAuthentication</faultcode>
<faultstring>The security token could not be authenticated or
authorized</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>

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.