{"version":"2.1.260","anchor":"vertexbedrockfoundry-inference-settings-hardened","canonical_anchor":"vertexbedrockfoundry-inference-settings-hardened","heading":"Vertex\/Bedrock\/Foundry inference settings hardened","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/vertexbedrockfoundry-inference-settings-hardened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Vertex\/Bedrock\/Foundry inference settings hardened\n\nSeveral Vertex\/Bedrock\/Foundry settings are now more locked down with consent and redaction changes.\n\nSeveral Vertex, Bedrock, and Foundry inference settings are now more locked down: Vertex's `region`\/`baseUrl` and Bedrock's `ssoRegion` gained `readers: [\"desktop\", \"m365\"]` restrictions and\/or `requiresUserConsent` on remote policy. The Vertex OAuth `clientSecret` field's redaction changed from `redact: \"drop\"` to `redact: \"presence\"`, with a new hint that Google treats installed-app client secrets as non-confidential, so it may be set from hosted config.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}