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

Grant SQL server identities the DirectoryReader role #1421

Open
3 tasks done
nilsgstrabo opened this issue Aug 5, 2024 · 0 comments
Open
3 tasks done

Grant SQL server identities the DirectoryReader role #1421

nilsgstrabo opened this issue Aug 5, 2024 · 0 comments
Assignees

Comments

@nilsgstrabo
Copy link
Contributor

nilsgstrabo commented Aug 5, 2024

Today the deploy-database GH actions for radix-cost-allocation and radix-vulnerability-scanner is unable to create users (CREATE USER FROM EXTERNAL PROVIDER) because the SQL Server identity is missing the DirectoryReader role, ref. https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-aad-service-principal?view=azuresql

Omnia has created an Entra security group which is member of this role, and is intented to grant service principals (managed identities/app registrations) membership to this role. Adding as SP to this group is a manual process which involved sending an email to [email protected] (ref https://docs.omnia.equinor.com/governance/iam/App-Admin-Consent/).

Tasks:

  • Send email to [email protected] requesting the SQL server identities to be member of the Entra Group
  • Add information in radix-private on how to request DirectoryReader role membership.
  • Update readme in radix-vulnerability-scanner and radix-cost-allocation with a description on what permissions are required, and perhaps a link to radix-private, which can contain more Equinor specific details.
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