Spring'18 - "Login As' event type is not generated in Event log monitoring.
Last updated 2018-02-27 ·Reference W-4557087 ·Reported By 2 users
With the Spring '18 release customers were unable to see ‘Login As’ event type in Event Log Files though they could see all other event types. This was fixed on 2/23/2018.
We can perform ‘Login As’ event in both regular and community context.
1.) As an admin, you can log in as another standard user.
2.) log into a community from a Contact using ‘Login to a community as User’ option.
Both these events cannot be seen in event monitoring files.
LoginAs is captured in Setup Audit Trail, and it shows who logged in as whom in the org.
Setup Audit Trail captures when Login As is used from all of the above scenarios. Some values in the Login As Event Log File, for example SESSION_KEY, LOGIN_KEY are not available in the Setup Audit Trail. Customers can download Setup Audit Trail from the Set Up menu or via API. Setup Audit Trail trail is available for up to 180 days.
For more information see:
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.