EBS WSH/OTM Integration Fails With 'Invalid User Name And Password. Please Try Again' Due To OTM Disable Message And Disable Custom HTTP Credentials Opt In Features
(Doc ID 2767572.1)
Last updated on AUGUST 15, 2023
Applies to:Oracle Shipping Execution - Version 12.1.3 to 12.2.10 [Release 12.1 to 12.2]
Information in this document applies to any platform.
From OTM 20C, the 'DISABLE MESSAGE CREDENTIALS' and 'DISABLE CUSTOM HTTP CREDENTIALS' features are by default enabled or 'opted in', therefore it is expecting the OTM credentials to be encoded using HTTP Basic Authentication.
When upgrading to OTM 21A and running the Shipping Transportation Outbound Interface, the program ends in error and cannot interface data to OTM. Error is seen in the XML and Shipping Transportation Outbound log file as follows:
<StackTrace>Invalid user name or password. Please try again.</StackTrace>
Shipping Transportation Outbound Log shows the following error:
SEVERE: java.io.FileNotFoundException: ./config/jps-config.xml (No such file or directory)
For more detailed information on the processing of deliveries in this batch
Please look at Bpel Instance Id :******
OTM Transmission Id null
ReturnStatus from BPEL process: U
Upgrade to OTM 21A
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