OnBase: Logins from Web Client are logged as Core Services instead of HTML Web Client in the hsi.securitylog file when using IdP authentication
Description
When a user logs into the Web Client using IdP authentication, the event logged in the hsi.securitylog file is Core Services instead of HTML Web Client.
The event is logged as HTML Web Client when using authentication other than IdP, such as OnBase authentication or AD Authentication.
Resolution
This occurs due to a known issue (CSFMD-2392).
To resolve this issue, upgrade to OnBase Foundation 24.1 or higher.
To work around this issue, use an authentication type other than IdP authentication. This will cause the event to be logged as HTML Web Client.
Related Articles
OnBase Reference Guide
OnBase Reference Guide MRG
OnBase: Blank screen when attempting to view Epic Documents in Web Client after installing Web Server
Description After a new installation of Web Server, when attempting to view documents from Epic in OnBase Web Client, a blank screen is presented: Additionally, when attempting to view the document directly through Epic Media Manager, a blank screen ...
OnBase: PDF documents fail to load in the Web Client after upgrading to version 25.1.3.1000 or higher
Description After upgrading to OnBase 25.1.3.1000 or higher, PDFs Documents does not load in the OnBase Web Client. Instead, only the gray loading screen is displayed, and the thumbnail appears with a red X. The following screenshot demonstrates the ...
OnBase: Redaction button will not stay selected in the Web Client
Description In OnBase 18 Web Client, when opening a document within the Legacy Viewer (ActiveX), it is possible to select the redaction button once and continue adding redactions one after another. However, in OnBase Foundation Web Client it is ...
After changing a user name in Active Directory, the user is unable to login to the OnBase Web Client
We have seen this issue in Technical Support where a users account was renamed in Active Directory and then they are no longer able to login to OnBase via the Web Client. The reason for this issue is that the old user account was cache on the Web ...