Korath
Platinum Üye
- Katılım
- 13 Şub 2026
- Mesajlar
- 144
- Beğeniler
- 45
- İletişim
Hey everyone,
I've been working on a Vanguard emulator and managed to get the authentication flow working:
- Auth: HTTP 200
- Access: HTTP 200 (token saved, session active)
- Heartbeat: every 45s, HTTP 200
The AuthenticationRequest includes all required fields:
- Field 1: machine_id (base64 random)
- Field 2: OSInfo (variant=6, arch=2, version=10.0.19045)
- Field 4: JWT (RSO token, cid=valorant-client)
- Field 5: Client RSA public key (SPKI base64)
- Field 6/7: Version 1.18.4.47
- Field 8: com.riotgames.valorant
- Field 9: boot_state=3
- Field 13: external_sid (UUID)
- Field 14: Security flags (HVCI, IOMMU, SB, VBS, TPM2)
- Field 15: metadata (ht = base64(sha256(hwid)[:20]))
Encryption: RG envelope (RSA-OAEP-SHA512 + AES-256-GCM), server public key matches.
Despite the session being fully active, VALORANT won't let me queue for a match (VAL5 error).
My questions:
1. Are there additional fields required in AuthenticationRequest that I'm missing? (like CoreInfo, MemoryInfo, ephemeral_identifiers)
2. Does the server send tasks/modules that MUST be completed before queue unlock?
3. Are the new capabilities (DEP, CFG, CET, SMEP, etc.) already enforced?
4. Is there a specific heartbeat response that needs to be parsed/handled?
Any help would be massively appreciated. Willing to share more details in DM.
Thanks!
I've been working on a Vanguard emulator and managed to get the authentication flow working:
- Auth: HTTP 200
- Access: HTTP 200
(token saved, session active)- Heartbeat: every 45s, HTTP 200
The AuthenticationRequest includes all required fields:
- Field 1: machine_id (base64 random)
- Field 2: OSInfo (variant=6, arch=2, version=10.0.19045)
- Field 4: JWT (RSO token, cid=valorant-client)
- Field 5: Client RSA public key (SPKI base64)
- Field 6/7: Version 1.18.4.47
- Field 8: com.riotgames.valorant
- Field 9: boot_state=3
- Field 13: external_sid (UUID)
- Field 14: Security flags (HVCI, IOMMU, SB, VBS, TPM2)
- Field 15: metadata (ht = base64(sha256(hwid)[:20]))
Encryption: RG envelope (RSA-OAEP-SHA512 + AES-256-GCM), server public key matches.
Despite the session being fully active, VALORANT won't let me queue for a match (VAL5 error).
My questions:
1. Are there additional fields required in AuthenticationRequest that I'm missing? (like CoreInfo, MemoryInfo, ephemeral_identifiers)
2. Does the server send tasks/modules that MUST be completed before queue unlock?
3. Are the new capabilities (DEP, CFG, CET, SMEP, etc.) already enforced?
4. Is there a specific heartbeat response that needs to be parsed/handled?
Any help would be massively appreciated. Willing to share more details in DM.
Thanks!
