{"version":"2.1.257","anchor":"new-wif-workload-identity-federation-profile-credential-pa","canonical_anchor":"new-wif-workload-identity-federation-profile-credential-pa","heading":"New WIF (Workload Identity Federation) profile-credential path for remote settings","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/new-wif-workload-identity-federation-profile-credential-pa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### New WIF (Workload Identity Federation) profile-credential path for remote settings\n\nRemote settings can authenticate with a Workload Identity Federation bearer token when no API key or OAuth token exists.\n\nRemote settings fetching now has a fallback credential path for Workload Identity Federation (WIF): when no API key or user OAuth token is available, it obtains a bearer token via `getWIFTokenCache`\/`getWIFCredentials` and marks the request with `profileBearer: true`. A 401 with this credential triggers one forced refresh and retry; if the settings endpoint rejects the refreshed token too, a `settingsBearerRejected` latch stops further retries with that credential until the next sign-in or restart.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 4\/5\n- Signal: 4\/5"}