Cannot change username of previously, NOT CURRENTLY, federated user.

[SKlein-1428]

Description:

Want to change username. Cannot change username. Says "federated users can't change username. Federation is not active. Once disabled, it should not lockdown features.

Steps to reproduce:

1. Enable federation.
2. Talk to one person, for any amount of time, from a federated server.
3. Disable federation.
4. Try to change username.
5. Error message.

Expected behavior:

Once Federation is disabled, users can change username again, as they no longer need consistent usernames across platforms.

Actual behavior:

Users can't change username if they are "federated" at any point.

Server Setup Information:

• Version of Rocket.Chat Server: 8.2.1
• License Type: Starter or Community, whichever one lets you use the Push Notification API. Which is also still broken but, that's not the point of this report.
• Number of Users: 8
• Operating System: Ubuntu Server Current LTS AO 2026-24-04 64bit
• Deployment Method: Docker
• Number of Running Instances: 1
• DB Replicaset Oplog: .
• NodeJS Version: .
• MongoDB Version: .

Client Setup Information

• Desktop App or Browser Version: Both Rocket.Chat desktop 4.12.1-alpha.6 and Firefox 148.0.2
• Operating System: Kicksecure Distro morph from Debian trixie

Additional context

Less Ableism would be great now that I had someone help me fill out your template to the best of my ability.

Relevant logs:

"For more information about collecting logs please see: https://rocket.chat/docs/contributing/reporting-issues#gathering-logs" - this leads to, not a page about gathering logs.
You demand perfection from bug reports and do not exhibit it in documentation. Frustrating. Please address documentation issues if you wish to enable those of us with less capacity to follow your expectations.

[JarvisX-Z]

This seems to be caused by a persistent federation flag rather than checking the current federation state dynamically.

If the system is marking users as "federated" at any point and not revalidating after federation is disabled, it can incorrectly lock username updates.

A better approach could be:

• Validate federation status at runtime instead of relying on historical flags
• Or reset federation-related constraints when federation is disabled

Possible fix:
Check the current federation configuration before blocking username changes instead of relying on past federation state.

[ayyagarisujanreddy123]

Working on it!!