Detecting a Masquerade vs a normal login

There's masquerade service which is responsible to say if user is masquerading

You can see how it working in https://www.drupal.org/project/masquerade_log →

Ref https://git.drupalcode.org/project/masquerade_log/-/blob/8.x-1.x/src/Mas...

Thanks @ andypost → .

I have had a look at the Masquerade Log module → and from what I can see, it might be possible to intercept the creation of the DBLog entries using the ECA Log sub-module but that would mean essentially using ECA to intercept all log messages at creation time just to pick the original UID and create a token from it which we can then play with in ECA.

My gut feeling is that it might be a whole lot more efficient for the Masquerade module itself to simply populate a couple of tokens say:

[masquerade_original_uid] - the original user before the masquerade.
[masquerade_current_uid] - the user as a result of the masquerade.

Both of these only being populated during a live masquerading session.

This way, we can use them immediately in ECA and a load of other places too.

Would that be a good proposal?

Not sure tokens useful here as masquerade has context already and that's session specific property

I'm not sure you want mean there @andypost → ?

Before Masquerade does it's business of masquerading surely it first takes a note of the existing user's ID in order in order that it can switch back to being them at the end of the session?

Thus, it (Masquerade) knows both values for UIDs and therefore could easily set the two tokens, un-setting them again at the session.

What am I missing here?