My Oracle Support Banner

If OBDx Uses OAM Authentication, Performance Issue Observed in User Management Screen When Party ID Is Used to Search User (Doc ID 2669778.1)

Last updated on MAY 20, 2020

Applies to:

Oracle Banking Digital Experience - Version 18.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

When attempting to search user through PartyID on User Management screen from admin, system is failing on "/digx/v1/users?partyId=<PARTY_ID>&userType=retailuser&locale=en" call exactly after 4 minutes. Response is not received for this call within 4 minutes and API fails with error response "Session Expired" on browser.. On network log
the following error occurs.

ERROR
-----------------------
DIGX_FW_NON_002


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. As admin user navigate to user management screen.
2. Search user of a particular party id.
3. Observe that REST request fails with above mentioned error.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, admin users cannot search users for a party.

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
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.