{"version":"2.1.269","anchor":"rename-session-now-validates-session-id-and-records-host-aut","canonical_anchor":"rename-session-now-validates-session-id-and-records-host-aut","heading":"rename_session now validates session_id and records host-authored renames","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/rename-session-now-validates-session-id-and-records-host-aut","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### rename_session now validates session_id and records host-authored renames\n\nrename_session now checks the session id and logs host-initiated renames separately\n\n**What**\n\nThe control-channel `rename_session` request now rejects a rename if the `session_id` it specifies doesn't match the current session. Separately, when a rename originates from a 'host' source, it's now also recorded and propagated through a new dedicated call, in addition to the existing rename mechanism.\n\n**Why**\n\nThis prevents a session from being renamed by a mismatched request and adds proper tracking for renames initiated by the host application.\n\n- Area: SDK\n- Names: `rename_session`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}