azure sql login retry mania :D
We use a azure sql data source with entra id mfa login that pops to the browser. Problem is when session lifetime ends (our CA policy has 8 hours for priviliged accounts) then RDM tries to re-authenticate. This usually happens during the night when I'm not at my computer, so in the morning my browser has hundreds of tabs trying to authenticate. Maybe it would be better if it asks for confirmation before popping the login to browser? or give up after one try?
891b3269-c2d1-46f0-8170-a299b05c2b2c.png
All Comments (1)
That's an interesting one. We don't control the auth flow for SQL Azure, that's handled by Microsoft. What we do control is when we connect to the database.
Most likely, what’s happening here is that either the auto-refresh or a dashboard with a refresh timer is trying to pull updated data. The first step in that process is to establish and open a connection, which triggers the auth flow and eventually crashes or times out.
We’d need to detect this situation and stop the auto-refresh or dashboard refresh until the user performs an action (like refresh or edit). At that point, we can restart the refresh flow. The user would be prompted once, and it should continue normally from there.
This is all theoretical for now, we’d need to reproduce the exact issue with a much shorter token lifetime (a few minutes) to confirm.
As a workaround, I suggest setting your RDM to Offline before leaving for the day. You could also try the auto-go offline feature, it might actually do the trick. Your RDM would go offline once the first token lifetime expires, and in the morning, you’d just refresh to go back online. Give it a try and let me know if it helps.
Best regards,
Stéfane Lavergne