<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secondary-Roles on Kevin Keller</title><link>https://kevinkeller.org/tags/secondary-roles/</link><description>Recent content in Secondary-Roles on Kevin Keller</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>kellerkev@gmail.com (Kevin Keller)</managingEditor><webMaster>kellerkev@gmail.com (Kevin Keller)</webMaster><copyright>© 2026 Kevin Keller</copyright><lastBuildDate>Fri, 13 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kevinkeller.org/tags/secondary-roles/index.xml" rel="self" type="application/rss+xml"/><item><title>From SAML Login to Snowflake as the User: Entra ID Passthrough Without the Secondary-Role Trap</title><link>https://kevinkeller.org/posts/snowflake-saml-oauth-passthrough-entra-id/</link><pubDate>Fri, 13 Nov 2026 00:00:00 +0000</pubDate><author>kellerkev@gmail.com (Kevin Keller)</author><guid>https://kevinkeller.org/posts/snowflake-saml-oauth-passthrough-entra-id/</guid><description>Your web app signs users in with SAML, and now it needs to query Snowflake as each user. A SAML assertion can&amp;rsquo;t be exchanged for an OAuth token, and the usual role-any shortcut leaves every other role active, ACCOUNTADMIN included. A tested pattern with Entra ID: a silent OIDC hop, role-scoped tokens, and a second External OAuth integration that puts Snowflake in charge of which roles the app may use.</description></item></channel></rss>