Manage big data cluster access in Active Directory mode
Applies to: SQL Server 2019 (15.x)
The Microsoft SQL Server 2019 Big Data Clusters add-on will be retired. Support for SQL Server 2019 Big Data Clusters will end on February 28, 2025. For more information, see Big data options on the Microsoft SQL Server platform.
This article describes how to add new Active Directory groups with bdcUser roles in addition to the ones provided during deployment through the clusterUsers configuration setting.
Do not use this procedure to add new Active Directory groups with bdcAdmin role. Hadoop components, such as HDFS and Spark, allow only one Active Directory group as the superuser group - the equivalent of the bdcAdmin role in BDC. In order to grant additional Active Directory groups with bdcAdmin permissions to the big data cluster after deployment, you must add additional users and groups to the already-nominated groups during deployment. You can follow same procedure to update the group membership that have bdcUsers role.
Two overarching roles in the big data cluster
Active Directory groups can be provided in the security section of the deployment profile as part of two overarching roles for authorization within the big data cluster:
clusterAdmins: This parameter takes one Active Directory group. Members of this group have the bdcAdmin role, meaning they get administrator permissions for the entire cluster. They have sysadmin permissions in SQL Server, superuser permissions in Hadoop Distributed File System (HDFS) and Spark, and administrator rights in the controller.
clusterUsers: These Active Directory groups are mapped to bdcUsers role in BDC. They are regular users, without administrator permissions in the cluster. They have permissions to log in to the SQL Server master instance but, by default, they have no permissions to objects or data. They are regular users for HDFS and Spark, without superuser permissions. When connecting to the controller endpoint, these users can only query the endpoints (using azdata bdc endpoints list).
To grant additional Active Directory groups bdcUser permissions without altering group memberships inside Active Directory, complete the procedures in the next sections.
Grant bdcUser permissions to additional Active Directory groups
Create a login for the Active Directory user or group in the SQL Server master instance
Connect to the master SQL endpoint by using your favorite SQL client. Use any administrator login (for example,
AZDATA_USERNAME, which was provided during deployment). Alternatively, it could be any Active Directory account that belongs to the Active Directory group that's provided as
clusterAdminsin the security configuration.
To create a login for the Active Directory user or group, run the following TSQL command:
CREATE LOGIN [<domain>\<principal>] FROM WINDOWS;
Grant the desired permissions in the SQL Server instance:
ALTER SERVER ROLE <server role> ADD MEMBER [<domain>\<principal>]; GO
For a complete list of server roles, see the corresponding SQL Server security topic here.
Add the Active Directory user or group to the roles table in the controller database
Obtain the controller SQL server credentials by running the following commands:
a. Run this command as a Kubernetes administrator:
kubectl get secret controller-sa-secret -n <cluster name> -o yaml | grep password
b. Base64 decode the secret:
echo <password from kubectl command> | base64 --decode && echo
In a separate command window, expose the controller database server port:
kubectl port-forward controldb-0 1433:1433 --address 0.0.0.0 -n <cluster name>
Use the preceding connection to insert a new row in the roles and active_directory_principals tables. Type the REALM value in uppercase letters.
USE controller; GO INSERT INTO [controller].[auth].[roles] VALUES (N'<user or group name>@<REALM>', 'bdcUser') GO INSERT INTO [controller].[auth].[active_directory_principals] VALUES (N'<user or group name>@<REALM>', N'<SID>') GO
Verify that the members of the group that you added have the expected bdcUser permissions by logging in to the controller endpoint or authentication to the SQL Server master instance. For example:
azdata login azdata bdc endpoints list
Submit and view feedback for