{"version":"2.1.248","anchor":"credentials-could-survive-token-changes-off-in-this-build","canonical_anchor":"credentials-could-survive-token-changes-off-in-this-build","heading":"Credentials could survive token changes, off in this build","tier":"soon","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/credentials-could-survive-token-changes-off-in-this-build","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Credentials could survive token changes, off in this build\n\nStored credentials could survive a token change, but not in this build.\n\n**What**\n\nA new option decides whether stored credentials are kept when the token they belong to changes. It is controlled by the server-side gate `tengu_still_kestrel`, and with no server value the compiled fallback is false, so credentials are not kept in this build.\n\n**Details**\n\n- The result is computed once and cached on the config object as `keepAcrossTokenChanges`.\n- If the gate reader returns nothing at all, the helper also returns false.\n\n**Evidence**\n\n`keepAcrossTokenChanges`\n\n- Flag `tengu_still_kestrel`: Gate removed from the code (read for one account on one subscription tier against v2.1.248; this account: on, anonymous baseline: on, compiled default: not a boolean we can read)\n- Area: Auth\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}