My Oracle Support Banner

Problem Logging In RESA With A Secure OID Connection Established - The TrustAnchors Parameter Must Be Non-Empty (Doc ID 2884251.1)

Last updated on JULY 22, 2022

Applies to:

Oracle Retail Sales Audit - Version 19.0.1 and later
Information in this document applies to any platform.


On : 19.0.1 version, Other

Problem logging in RESA with a secure OID connection established

Connecting RESA to OID, using a secure connection gives this error: " the trustAnchors parameter must be non-empty"


 " the trustAnchors parameter must be non-empty"

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

 1) Deploy FMW Infra + Domain as instructed on the RESA installation guide
 2) Create OID wallet with custom CA 
 3) Activate secure connections, on OID port 3132, with the created wallet
 4) Create java keystore for weblogic, using same custom CA created in 2)
 5) Register custom CA in the java wallet ($JAVA_HOME/jre/lib/security/cacers)
 6) On weblogic AdminServer and resa managed server activate this options:

Keystore: Custom Identity and Java Standard Trust
Hostname Verification: None

 7) Started Adminserver, and checked all users and groups from OID are loaded (Security realms > myrealm > Users and groups)
 8) Started resa managed server, no errors in log
 9) Load RESA app, try to login and get stuck on the error " the trustAnchors parameter must be non-empty"


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

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