Description:
When I rename a Profile in RADIUSdesk, the custom components previously associated with that Profile become unavailable.
After investigating the database, I found that the radusergroup table does not update the existing records with the new Profile name. Instead, it creates new records with the new Profile name while keeping the old records with the original Profile name. This causes the Profile to lose its component bindings.
Expected behavior: The username field in radusergroup should be updated with the new Profile name, preserving all component associations.
Actual behavior: New records are created with the new Profile name, and old records remain unchanged, resulting in lost associations.