FiveM & RedM Steam Authentication Update
Artifact 38004+, steam_webApiKey Deprecated & sv_enforceSteamAuth
Cfx updated the Steam authentication flow for FiveM and RedM on November 4, 2026. Players joining servers that require Steam authentication may now be prompted to link their Steam account to their FiveM or RedM account before connecting. For server owners, the important part is a hard artifact requirement and a deprecated config key.
The announcement comes from Cfx - see the Cfx announcements category and the FXServer server commands documentation.
🔐 What Changes For Players
- Servers that require Steam authentication may prompt players to link their Steam account to their FiveM or RedM account before connecting.
- Players follow the on-screen instructions to continue connecting to the server.
The linking step happens before the player reaches the server, so it is not something a resource can handle for them. If your community sees players stuck at the connection screen, the first question is whether they completed the Steam link prompt - not whether the server is down.
⚠️ What Changes For Server Owners
steam_webApiKeyis deprecated.- Existing servers that rely on Steam IDs must update their FXServer artifact to version 38004 and above to avoid service interruptions.
- New servers that wish to require Steam authentication must add
set sv_enforceSteamAuth trueto their config.
This is the critical distinction: updating the artifact is not optional for servers that depend on Steam identifiers. The new client flow and the old server expectation do not line up, and the failure mode is players being unable to connect even after they have linked their account. The artifact update is what makes the server side understand the new authentication path.
The deprecation of steam_webApiKey is the other half. New servers should use sv_enforceSteamAuth true rather than relying on a Web API key to request Steam identifiers. If you maintain older setup guides or a server template, this is the line that needs changing.
✅ Server Owner Checklist
- Check your current artifact version. If you are below 38004 and your server relies on Steam IDs, update before your next busy session.
- Update the artifact, not just txAdmin. txAdmin can be current while the FXServer build underneath is still too old. The announcement specifically calls out the server artifact version.
- Add
set sv_enforceSteamAuth truefor new Steam-required servers. Do not copy an oldsteam_webApiKeysetup into a new server and assume it still works. - Keep your old config until you have tested.
steam_webApiKeyis deprecated, not necessarily an immediate removal. Update the artifact first, test a real connection, then clean up the config. - Tell players about the linking prompt. A short announcement with a screenshot of the Steam link screen prevents a wave of "server won't let me join" reports.
- Make sure Steam is running and logged in. The linking flow depends on the player's Steam account, so "restart Steam and try again" is a reasonable first troubleshooting step for client-side failures.
- Test with a Steam-required server before the update window. A local or staging server on artifact 38004+ is the cheapest way to confirm your config and player flow before exposing it to the community.
- Keep a rollback plan. Artifact updates can interact with resources and framework versions. Have a known-good build and backup before changing a live server.
🧩 Why This Matters Beyond Login
Steam identifiers are used for more than the connection screen. Whitelists, bans, VIP checks, character ownership and framework account tables can all key off a Steam identifier. If the server is not producing the identifier the new client flow expects, the symptom can look like a framework bug: a player connects but their framework account does not resolve, or an allowlist that should match does not.
That makes this an "update and verify" change rather than a "set it and forget it" change. After updating, check that a known player can connect, that their identifier still resolves, and that your allowlist or whitelist accepts them. Testing only the connection screen is not enough if your community depends on Steam-linked accounts.
🖥️ Recommended Rollout
- Legacy FiveM and RedM: update FXServer to 38004 or newer.
- FiveM for GTAV Enhanced: update to the current Cfx Server build through your normal artifact channel.
- New Steam-required servers: configure
set sv_enforceSteamAuth truefrom the start. - Existing Steam-required servers: update the artifact, test a Steam-linked account, then remove reliance on
steam_webApiKey. - Players: update the FiveM or RedM client, keep Steam open, and complete the link prompt when it appears.
Running a FiveM or RedM community? NolimitHost FiveM server hosting keeps your server on current builds with fast high-clock CPUs, NVMe storage, DDoS protection and automated backups - and RedM hosting is available too.
Conclusion
The November 4, 2026 Steam authentication update introduces an account-linking prompt for players joining Steam-required FiveM and RedM servers. Server owners must update to FXServer artifact 38004 or above if they rely on Steam IDs, steam_webApiKey is deprecated, and new Steam-required servers should use set sv_enforceSteamAuth true. Test a real Steam-linked account after updating - not just the connection screen.
For the rest of October's platform changes, see our server metadata Portal update, txAdmin 8.1.2 security release and October Community Spotlight breakdowns.