Implementing Easy Anti Cheat in a client-server unreal engine game, how are we supposed to get the token and EOS product ID to call EOS_Connect_VerifyIdToken?

Context: PC game, using unreal engine 5, client-server model.

I am Aware EOS_Auth_CopyIdToken exists, my question is: Is is mandatory to get this on the client and send it to the server like in the Sample project? Does the EOS subsystem do something like this already that I have missed? What happens if a client manages to skip that message somehow? Will it never get registered to anti cheat?

Given the context of an UE game, and given that to call EOS_AntiCheatServer_RegisterClient we just need an EOS_ProductUserId, would it be ok to register a client getting the product user id on the server from IUniqueNetIdEOS (we get it from the PlayerState->GetUniqueId() and cast it ) and hard coding the client platform to windows as for now that’s the only platform supported?

And am I absolutely required to validate the web token myself even if we don’t need it to register to anti cheat ?

This doesn’t require the client to initiate the flow to register to anti cheat but I wonder if this fundamentally flawed or not. Some guidance on what to do here would be appreciated.

Hey, on your client, you should call EOS_Connect_CopyIdToken (not EOS_Auth_CopyIdToken - EOS_Auth is for Epic Account Services, EOS_Connect is for Game Services). Pass the token to the server, and on the server you should call EOS_Connect_VerifyIdToken before using the EOS_ProductUserId. You could use the FUniqueNetIdEOS directly to get the EOS_ProductUserId, but the safest approach is to copy the token and verify it. Using the token is not a requirement, but a recommendation.