We got an event:
{
"date": "...",
"type": "flo",
"description": "Invalid SessionIndex/NameID",
"connection_id": "",
"client_id": "...",
"client_name": "...",
"ip": "...",
"user_agent": "Edge 146.0.0 / Windows 10.0.0",
"details": {
"allowed_logout_url": []
},
"hostname": "...",
"user_id": "",
"user_name": "",
"$event_schema": {
"version": "1.0.0"
},
"environment_name": "prod-us-1",
"log_id": "90020260415064732185324000000000000001223372168442629092",
"tenant_name": "...",
"_id": "90020260415064732185324000000000000001223372168442629092",
"isMobile": false,
"location_info": {},
"id": "90020260415064732185324000000000000001223372168442629092"
}
the context had:
{
"allowed_logout_url": []
}
The IP address points to a shared IP used by the partner whose system is providing the SAML connection, and that partner also provides the same browser to pretty much everyone served by that IP address, so it isn’t terribly helpful.
It might be possible for us to time-correlate to other logs to our website, but I’m not terribly optimistic.