Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Privileged identity management (PIM) and ADS do not play well #25640

Open
shahiddev opened this issue May 15, 2024 · 0 comments
Open

Privileged identity management (PIM) and ADS do not play well #25640

shahiddev opened this issue May 15, 2024 · 0 comments

Comments

@shahiddev
Copy link

Type: Bug

Hi,
We use Entra Privileged Identity Management (PIM) to allow our team to be added to groups that have elevated privs on our SQL DBs in a JIT manner.

When a user is granted access via PIM their new permissions are not reflected in ADS unless they first clear the token cache, restart ADS and then re-sync their account.

Up until version 1.43 all we had to do was to remove and re-add the Azure account in ADS.
All versions since 1.43 this process has not longer worked and needs the explicitly token cache clearing and restarting ADS which is not ideal
This issue is related to one I reported a long time ago that was closed

This is an issue with the way the token's are being cached - I'm unclear as to what changed since 1.43 that has broken the previous behaviour - potentially the switch related MSAL ?

Azure Data Studio version: azuredatastudio 1.48.0 (4970733, 2024-02-27T00:05:08.293Z)
OS version: Windows_NT x64 10.0.22621
Restricted Mode: No
Preview Features: Enabled
Modes:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant