My Oracle Support Banner

E1:BSSV: Unable To Test Published Business Service Using SoapUI: Get error "Failed to assert identity with UsernameToken" (Doc ID 1400178.1)

Last updated on OCTOBER 10, 2023

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.

Symptoms

Symptom 1.  Using 8.98.4.2 with WLS 10.3.2. Unable to test supplier BSSV/Webservice on the server using SoapUI utility and you are receiving the below error message. You were able to test the web service a couple of weeks back. There was a new update package for custom BSSV's for deployment, but since then, have built a new bssv package without any custom objects and re-deployed and still getting the following error:

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<faultcode>wsse:FailedAuthentication</faultcode>
<faultstring>Failed to assert identity with UsernameToken.</faultstring>
</env:Fault>
</env:Body>
</env:Envelope>


BSSV Log shows this error:

17 Jan 2012 16:22:54,664 [SEVERE] - [NET] JdeNetConfig: ClassNotFoundException com.jdedwards.runtime.virtual.xapi.PublishedMessageProcessor for newInstance, com.jdedwards.runtime.virtual.xapi.PublishedMessageProcessor java.lang.ClassNotFoundException: com.jdedwards.runtime.virtual.xapi.PublishedMessageProcessor
17 Jan 2012 16:22:54,664 [MANDATORY] - [NET] Created new JdeServerListenerThread, port=6014
17 Jan 2012 16:22:54,664 [MANDATORY] - [NET] Created new JdeServerListener, port=6014, maxConn=200, maxQueue=100
17 Jan 2012 16:24:24,820 [SEVERE] - [INTEROP] enterpriseServer property not found in the INI file com.jdedwards.system.connector.dynamic.InvalidConfigurationException: enterpriseServer property not found in the INI file

A) Another customer had the same error within JDeveloper 12.1.3.0 using Tools 9.2.x and E1 9.2. Trying to create a new E1 Class Business Function value object in JDeveloper, and message pops up on screen in jdev as follows:

com.jdedwards.system.connector.dynamic.InvalidConfigurationException: enterpriseServer property not found in the INI file
at com.jdedwards.system.connector.dynamic.Connector.getProperties(Unknown Source)
at com.jdedwards.system.connector.dynamic.Connector.<init>(Unknown Source)


Symptom 2.
E900/8.98
The following error occurs: "The security token could not be authenticated or authorized" when trying to call the standard BSSV "getCustomerCreditInfo".

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><faultcode xmlns="">wsse:FailedAuthentication</faultcode><faultstring xmlns="">The security token could not be authenticated or authorized</faultstring><faultactor xmlns=""></faultactor></env:Fault></env:Body></env:Envelope>


BSSV log shows the below message:

22 Feb 2011 22:35:15,536 [Line ?] [AJPRequestHandler-RMICallHandler-6] [SEVERE] - [BASE] com.jdedwards.database.base.JDBException: [DATABASE_CONNECT_FAILED] Database Connection failed for DataSource System - 900. com.microsoft.sqlserver.jdbc.SQLServerException: The server version is not supported. The target server must be SQL Server 2000 or later.
com.microsoft.sqlserver.jdbc.SQLServerException: The server version is not supported. The target server must be SQL Server 2000 or later.


Symptom 3.
A new Business Services server has been configured using Weblogic.

When trying to connect to the enterprise server for business server security validation, the following error appears in the SOAPUI console:

env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<faultcode>wsse:FailedAuthentication</faultcode>
<faultstring>Failed to assert identity with UsernameToken.</faultstring>
</env:Fault>
</env:Body>
</env:Envelope>


Symptom 4.
After performing a tools upgrade, the customer encounters a BSSV error "The security token could not be authenticated or authorized" when testing using SoapUI.

<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<faultcode
xmlns="">wsse:FailedAuthentication</faultcode>
<faultstring
xmlns="">The security token could not be authenticated or authorized</faultstring>
<faultactor
xmlns=""/>
</env:Fault>
</env:Body>
</env:Envelope>


e1root.log shows the following:

2011 04:23:14,221 [SEVERE] - [INTEROP] Exception occurred while validating role and/or environment in Java Connector Login method:Unknown return code from role validation: 12 com.jdedwards.system.connector.dynamic.ServerFailureException: Exception occurred while validating role and/or environment in Java Connector Login method:Unknown return code from role validation: 12
com.jdedwards.system.connector.dynamic.ServerFailureException: Exception occurred while validating role and/or environment in Java Connector Login method:Unknown return code from role validation: 12


Security Kernel jde.log shows the following:

KSEC0000315 - Too few packets (3) passed to validate User, Role, Environment and Token; expecting 4 packets


Symptom 5:
Get error 'Failed to assert identity with UsernameToken' when starting the BSSV Server. -->  nothing on e1root.log for BSSV instnace.

 

Symptom 6:

WLS 12c and JAX-WS. Finished installing and deploying business services, but when testing using SoapUI 5.x getting the below error:

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<faultcode>wsse:FailedAuthentication</faultcode>
<faultstring>Failed to assert identity with UsernameToken.</faultstring>
</env:Fault>
</env:Body>
</env:Envelope>

 Symptom 7:

 E1BSSVAUthenticator2 or E1BSSV Authenticator was deployed manually and the  SOAPUI returns the following response:


<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
  <env:Body>
     <env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
        <faultcode>wsse:FailedAuthentication</faultcode>
        <faultstring>Failed to assert identity with UsernameToken.</faultstring>
     </env:Fault>
  </env:Body>
</env:Envelope>

 

 Symptom 8:

Using Tools Release 9.2.1.1 and Weblogic 12.1.3.0 that was installed using jdk 1.8. Database is SQL Server 2014 installed on Windows 2012 R2.

See the below error in SoapUI when trying to run the JPR01000-getAddressBookManager:

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<faultcode>wsse:FailedAuthentication</faultcode>
<faultstring>Failed to assert identity with UsernameToken.</faultstring>
</env:Fault>
</env:Body>
</env:Envelope>

 The BSSV Log shows the follow:

  

18 Apr 2017 12:49:24,817 [SEVERE] - [BASE] com.jdedwards.database.base.JDBException: [DATABASE_CONNECT_FAILED] Database Connection failed for DataSource Central Objects - DV920. com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "SQL Server returned an incomplete response. The connection has been closed.".
18 Apr 2017 12:49:24,817 [SEVERE] - [BASE] com.jdedwards.database.base.JDBException: [DATABASE_CONNECT_FAILED] Database Connection failed for DataSource Central Objects - DV920. com.jdedwards.database.base.JDBException: [DATABASE_CONNECT_FAILED] Database Connection failed for DataSource Central Objects - DV920.

  

 Symptom 9:

 

See the below error in SoapUI when trying to run the JPR01000-getAddressBookManager:

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<faultcode>wsse:FailedAuthentication</faultcode>
<faultstring>Failed to assert identity with UsernameToken.</faultstring>
</env:Fault>
</env:Body>
</env:Envelope>

 There is no error BSSV Log (e1root) nor WLS BSSV Logs (*.out and *.log). 

 

 Symptom 10:

After tools release upgrade SoapUI test is failing with

<faultcode>wsse:FailedAuthentication</faultcode>

<faultstring>Failed to assert identity with UsernameToken.</faultstring>

Also runtime metrics do not appear for BSSV server.

Health check fails for Login.

Symptom 11:

Unable to connect to BSSV after tools release update. Error "Failed to assert identity with UserNameToken"

This issue is after upgrade of tools release from 9.2.6.3/4 to 9.2.6.5. Built new BSSV package and deployed. After deploying, can no longer connect to BSSV and receive the following error message: 

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.