Heartbeat using wrong username

Heartbeat (on endpoint) does a checkup on the format of your username. It checks, if the SAMAccountname and Domain name differentes from the UPN. If case, it is different, it sends only the SAMAccountname to the Firewall. Then the firewall will match it against all AD Servers. Check your AD and this particular user. You find under Advanced View the SAMAccountname. 

yea, sAMAccountName is really in this format. Now the question is, how to handle this situation. Dont really want to change this variable in AD, it might breake some other service outside of Sophos stuff.

And why is Hearthbeat green, when almost every user failing to log in with HB?

doing this actually got me disconnecting from fw after few seconds i log in from Sophos Central. Had to fast delete fqdn record and newly added AD server :-D

ok that was not the case. I got disconnected when i try to list users on fw. What the hell? Maybe bug in new firmware?

gonna try workaround again tommorow then.

You mean disconnected by the webadmin or the entire client got disconnected? 

firewall logs me out for some reason, but thats topic for new thread. Lets focus on what we have here

problem persist even after adding workaround AD. HBs in log have still username in sAMAccountname, which is pure username without any domain.

If unauthenticated HBs are not problem for proper function of Sophos services, i would give up on this topic :-(

Did you add the server to the Authentication - Services list? 

uhm, i did not :-) alright, its really working as you said. Its also creating second user for everyone, but i dont think thats gonna be a problem. Thank you for being patient and of course for your help!

Ok this is a nice trick and my Hearbeat can authenticate now but the problem now is that I have the user twice on the FW. How can I solve this?

As far as i know, the new user can be used for everything. You need to delete the old (.local) user and the new user will be also matched by other facilities. 

its not really a problem actually. But if you want to go ahead and merge them, you should be more carefull before you delete them. Just check all services, what are asociated with old users, migrate them and then just simply delete them. Thats what i plan to do.

its not really a problem actually. But if you want to go ahead and merge them, you should be more carefull before you delete them. Just check all services, what are asociated with old users, migrate them and then just simply delete them. Thats what i plan to do.