Rider does not refresh credentials when Azure roles change in the portal
Hi all,
TL;DR - How can I force-refresh my Azure credentials in Rider?
My organization works with just-in-time access. This means I need to request some roles on my Azure account to be able to work with Azure infrastructure. I do this usually in the morning.
When I remember to request my roles first, and then I open rider second, all goes well
However if I forget to request my roles, open Rider and then change my roles in the portal, Rider does not pick up the role changes.
I have tried forcing a token/creds refresh using Tools > Azure > Sign out then Sign in. I tried both with Az cli and OAUTH token.
I also sign out, clean creds and sign in from az cli from my cmd. No luck
At some point the token Rider caches expires, and then it re-fetches it and starts working.
This is very irritating as you can imagine.
How can I force Rider to get my latest creds for Azure?
Please sign in to leave a comment.
Hello,
Thank you for raising this inquiry. Let me clarify how authentication and authorization workflows interact with Azure RBAC in this scenario:
When signing into Rider with your credentials, Rider utilizes your JSON Web Token (JWT) strictly for authentication purposes. This process confirms your identity to Azure Resource Manager but does not evaluate permissions. As outlined in Authentication vs. authorization, authorization – including Azure RBAC role validation – occurs exclusively server-side during resource access attempts.
In this case, Rider acts solely as an authentication client and does not participate in RBAC permission validation. It is just telling the server who the user is. Role assignment checks are performed dynamically by Azure Resource Manager during authorization. This process is detailed in How Azure RBAC determines if a user has access to a resource.
So there’s typically no need to refresh credentials in Rider to get new role assignments. I have confirmed this workflow in my environment.
In summary, this problem should not be related to Rider. You can use Azure CLI to verify role assignment and confirm if the same operation fails on Azure CLI. If yes, it's recommended to contact Azure support.
If not, please let me know. I will investigate further.
Thank you for the informative response.
I can confirm that the problem was related to network, not to Rider or even Azure. THe VPN I use to connect my Azure resources was falling out silently from time to time.
This item can be closed. Hope it helps someone.