My Oracle Support Banner

User Login Time Not Being Populated When Using Single Sign On (Doc ID 2410226.1)

Last updated on DECEMBER 12, 2023

Applies to:

Oracle Financial Services Revenue Management and Billing - Version and later
Information in this document applies to any platform.


Qn1:In our embedded installations, we can see that the user's last login in time is being populated in TABLE sc_user_char u.
but in a native installation, [ which is behind an apache web server with the OAM and WL plugins ], this value is not being populated.

It seems that this value only gets updated if the user logs in through the ORMB page: loginPage.jsp.
Also, it appears that unless loginPage.jsp is the first request, this value does not get updated.

For example, if we start a session by going to /ouaf/cis.jsp ( which redirects to the loginPage.jsp ), the value is not being updated.
Only if we go directly to /ouaf/loginPage.jsp does this value get updated.

In a single sign on (SSO) setup, we do not want users logging in via loginPage.jsp - if we send the user to this page, then they are signing in twice and that breaks the whole concept of single sign on.

How can we get the User Login Time to be populated when using SSO?
Qn2:Why is the user login time not saved when logging out of the application?


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.