Several internal services now receive login credentials directly instead of grabbing whatever token is lying around.
tengu_windows_credman Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.239: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.239. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
A build-wide switch, pinned once at startup, decides whether these call sites pass an explicit credentials object or fall back to reading ambient OAuth tokens. Affected: Grove settings and notice, voice stream, design session auth, bridge session fetch and patch, peer listing, tips prewarm.
- Grove's cached fetchers now key on
"account"and"config"instead of sharing one entry. - Startup also primes the credential-storage decision from a cached feature flag and loads remote settings earlier.
- Related telemetry name:
tengu_windows_credman.
tengu_windows_credman
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Signing back into the same account keeps a pending auto-resume
Both mention auth
-
v2.1.234
Token screen reports actual remaining validity
Both mention auth
-
v2.1.234
Setup-token login result carries the expiry
Both mention auth