Pulse displays username if the displayname is not available in the user sessions table and license report.
In this case both of them are not available in a tm1 session. The reason for this is discussed in the following topic User Session "?" in Pulse , highlighting the potential cause, to be thread handling delayed authentication or invalid authentication in TM1.
This raises the question, what causing the delay in tm1 when handling authentication.
These session can sometime be longer and gets picked up by Pulse.
We can’t treat this as a bug, since pulse try to sumarrize all the session data that TM1 provides.
We can ignore them or can be labelled as system (i.e. TM1) related.
This require further investigation to confirm the cause of the reported issue.
Please can you open an issue and provide a possible scenario when such sessions get reported.
thanks,
Johnson