Audit log missing details
I'm seeing some audit log entries with missing details. Is this a bug?
6 Replies
I'd also like to be able to tell which sign in method the user used to sign in. Is this possible? If not, is it something you might add?
Hi @Martin,
When an audit log has a user as
<unknown>, its for an M2M token/authencation.
However, M2M authentication should have an IP.
Can you locate another M2M authentication log that has an IP address?
I'd also like to be able to tell which sign in method the user used to sign in. Is this possible? If not, is it something you might add?This is currently not possible, but has been requested a few times. More extensive authentication analytics, that would include sign-in method analytics, is on our radar. I have noted your request down.
Are you sure that this is an M2M authentication? I'm not expecting my "InRange-Customer" API to be performing any M2M authentications.
These mystery logs do have an IP address, but I've redacted it in my screenshot in this public support forum. I'm hoping you can find it in your own logs given my application name and timestamp of this audit log.
These mystery logs do have an IP address, but I've redacted it in my screenshot in this public support forum.Aaah gotcha.
Are you sure that this is an M2M authentication? I'm not expecting my "InRange-Customer" API to be performing any M2M authentications.I can confirm that the log you shared is for an M2M authentication. A log with user
<unknown> (and no value for email, user ID and organizations) can only be achieved for an M2M authentication or an end-user that has now been deleted.
If the log was for an end-user that has now been deleted, the details of the log would say:
{name} was granted an access token to {app name}If the log was for an M2M authentication, the
details of the log would say:
was granted an access token to {app name}Which is what you have above. Please let me know if you have any other questions.
Okay cool, I think I understand what's going on here. Thanks for your help!
No worries @Martin