My Oracle Support Banner

When a User Tries To Log In With biometric, The Last_Logged_In_DateTime is Not Updating in The Table DIGX_UM_USERPROFILE (Doc ID 2853041.1)

Last updated on MARCH 02, 2022

Applies to:

Oracle Banking Digital Experience - Version 20.1.0.0.0 to 20.1.0.0.0 [Release 20]
Information in this document applies to any platform.

Symptoms

On : 20.1.0.0.0 version, Production Support

ACTUAL BEHAVIOR
---------------
When a user tries to log in with biometric, the Last_loggedin_DateTime is not updating in the table digx_um_userprofile.

EXPECTED BEHAVIOR
-----------------------
When a user tries to log in with biometric, the Last_loggedin_DateTime should be updated in the table digx_um_userprofile.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login in the OBDX application via biometric

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, the Last_loggedin_DateTime is not captured in the table digx_um_userprofile.

Changes

 No changes done to hardware/product or environment cause this issue.

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.