Security integrations: Sessions close when the backing integration is disabled or dropped (Pending)¶

Attention

This behavior change is in the 2026_07 bundle.

For the current status of the bundle, refer to Bundle history.

Disabling or dropping a security integration didn’t previously affect sessions already established by it. Snowflake now closes sessions backed by an OAuth, SAML, or OIDC security integration when that integration is disabled or dropped.

Before the change:: Disabling or dropping a security integration (OAuth, SAML, or OIDC) had no effect on existing sessions created using that integration. Those sessions continued to work normally until they expired naturally.
After the change:: When the 2026_07 behavior change bundle is enabled in your account, disabling or dropping the security integration that backs a session closes that session on its next request, forcing the client to re-authenticate.

This change closes a security gap: previously, an administrator disabling or dropping a security integration to cut off access did not invalidate sessions that were already established through it, allowing continued access after the integration was disabled or removed.

Ref: 2390