Date: Thu, 28 Mar 2024 17:11:34 +0000 (UTC) Message-ID: <1784845341.6690.1711645894784@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6689_1549594808.1711645894782" ------=_Part_6689_1549594808.1711645894782 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Beginning with Registry v2.0.0, authentication events are record= ed for logging and audit purposes. The following types of events are record= ed:
Authentication events are recorded by authenticated identifier (ie: $REM= OTE_USER), which may correlate to zero or more Organizational Identities, w= hich in turn may correlate to zero or more CO People.
To view authentication events associated with an individual's identifier= , find the appropriate Organizational Identity, then select the Id= entifiers tab. Select Authentication Events for the appr= opriate identifier.
Because identifiers can be registered in multiple COs (if organizational= identities are not pooled) or are implicitly available in all COs (if orga= nizational identifies are pooled), and because a login event is not correla= ted to a specific CO, any CO administrator with permission to view authenti= cation events can see all authentication events for an identifier visible t= o the CO, even if the user intended to login for access to another CO to wh= ich they happen to belong. The Registry log records will not indicate which= CO was accessed (though web server logs may hold this information).
Platform administrators may view the entire authentication event log via= Platform >> Authentication Events.
See Also: