Hi Naoki-san, 

Have a look at User's Last Log On Timestamp Impact https://community.rws.com/product-groups/tridion/tridion-docs/b/weblog/posts/automating-on-tridion-docs---ishremote-v8-0-with-modern-authentication-is-now-available. When the identity provider is not the built-in one (like ISHID or earlier ISHSTS), the timestamp is indeed not maintained as the CMS is not offering the authentication anymore. And this is advised as external identity provider have this as their main business goal.

A very fluffy idea was to extend Find-IshUser cmdlet but we never got it to top of the backlog. There is some data available in Access Management (typically https://ish.example.com/ISHAM/). Theoretically it is possible to link the user profiles (from ISHCM) with the login information (from ISHAM), so combining the two data silos. This was one of the ideas behind adding the OpenAPI proxy to Access Management $ishSession.OpenApiAM10Client.UsersGetAsync().GetAwaiter().GetResult() which of course requires Access Management administrator api privileges.

Best wishes,
Dave

Hi Naoki-san, 

Have a look at User's Last Log On Timestamp Impact https://community.rws.com/product-groups/tridion/tridion-docs/b/weblog/posts/automating-on-tridion-docs---ishremote-v8-0-with-modern-authentication-is-now-available. When the identity provider is not the built-in one (like ISHID or earlier ISHSTS), the timestamp is indeed not maintained as the CMS is not offering the authentication anymore. And this is advised as external identity provider have this as their main business goal.

A very fluffy idea was to extend Find-IshUser cmdlet but we never got it to top of the backlog. There is some data available in Access Management (typically https://ish.example.com/ISHAM/). Theoretically it is possible to link the user profiles (from ISHCM) with the login information (from ISHAM), so combining the two data silos. This was one of the ideas behind adding the OpenAPI proxy to Access Management $ishSession.OpenApiAM10Client.UsersGetAsync().GetAwaiter().GetResult() which of course requires Access Management administrator api privileges.

Best wishes,
Dave

Hi Dave,

Thank you for your clarification. Now, I understand the last log-on timestamp of TD15 well.

As a temporary solution, I retrieved the last log-on timestamp from the Access Management DB table directory. I hope the Find-IshUser cmdlet will be enhanced in the future.

Best regards,
Naoki