Import module activedirectory linux

Tutorial: Use Active Directory authentication with SQL Server on Linux

This tutorial explains how to configure SQL Server on Linux to support Active Directory authentication, also known as integrated authentication. For an overview, see Active Directory authentication for SQL Server on Linux.

This tutorial consists of the following tasks:

• Join SQL Server host to Active Directory domain
• Create Active Directory user for SQL Server and set SPN
• Configure SQL Server service keytab
• Secure the keytab file
• Configure SQL Server to use the keytab file for Kerberos authentication
• Create Active Directory-based logins in Transact-SQL
• Connect to SQL Server using Active Directory Authentication

Prerequisites

Before you configure Active Directory Authentication, you need to:

• Set up an Active Directory Domain Controller (Windows) on your network
• Install SQL Server
  • Red Hat Enterprise Linux (RHEL)
  • SUSE Linux Enterprise Server (SLES)
  • Ubuntu

  Join SQL Server host to Active Directory domain

  Join your SQL Server Linux host with an Active Directory domain controller. For information on how to join an active directory domain, see Join SQL Server on a Linux host to an Active Directory domain.

  Create Active Directory user for SQL Server and set SPN

  The following steps use your fully qualified domain name. If you are on Azure, you must create one before you proceed.

  1. On your domain controller, run the New-ADUser PowerShell command to create a new Active Directory user with a password that never expires. The following example names the account sqlsvc , but the account name can be anything you like. You’ll be prompted to enter a new password for the account.

  Import-Module ActiveDirectory New-ADUser sqlsvc -AccountPassword (Read-Host -AsSecureString "Enter Password") -PasswordNeverExpires $true -Enabled $true 

  1. This account supports Kerberos AES 128 bit encryption
  2. This account supports Kerberos AES 256 bit encryption

  setspn -A MSSQLSvc/: sqlsvc setspn -A MSSQLSvc/: sqlsvc 

  Note If you receive an error, Insufficient access rights , check with your domain administrator that you have sufficient permissions to set an SPN on this account. The account that is used to register an SPN will need the Write servicePrincipalName permissions. For more information, see Register a Service Principal Name for Kerberos Connections. If you change the TCP port in the future, you must run the setspn command again with the new port number. You also need to add the new SPN to the SQL Server service keytab by following the steps in the next section.

  Configure SQL Server service keytab

  Configuring Active Directory authentication for SQL Server on Linux requires an Active Directory user account and the SPN created in the previous section.

  If the password for the Active Directory account is changed or the password for the account that the SPNs are assigned to is changed, you must update the keytab with the new password and Key Version Number (KVNO). Some services might also rotate the passwords automatically. Review any password rotation policies for the accounts in question and align them with scheduled maintenance activities to avoid unexpected downtime.

  SPN keytab entries

  1. Check the Key Version Number (KVNO) for the Active Directory account created in the previous step. Usually it is 2, but it could be another integer if you changed the account’s password multiple times. On the SQL Server host machine, run the following commands:
     • The below examples assume the user is in the @CONTOSO.COM domain. Modify the user and domain name to your user and domain name.

  kinit user@CONTOSO.COM kvno user@CONTOSO.COM kvno MSSQLSvc/:@CONTOSO.COM 

  SPNs can take several minutes to propagate through your domain, especially if the domain is large. If you receive the error, kvno: Server not found in Kerberos database while getting credentials for MSSQLSvc/:@CONTOSO.COM , please wait a few minutes and try again.

  The above commands will only work if the server has been joined to an Active Directory domain, which was covered in the previous section.

  • \ — Active Directory user account
  • @CONTOSO.COM — Use your domain name
  • /kvno — Replace with the KVNO obtained in an earlier step
  • — Use a strong password

  ktpass /princ MSSQLSvc/:@CONTOSO.COM /ptype KRB5_NT_PRINCIPAL /crypto aes256-sha1 /mapuser \ /out mssql.keytab -setpass -setupn /kvno /pass ktpass /princ MSSQLSvc/:@CONTOSO.COM /ptype KRB5_NT_PRINCIPAL /crypto rc4-hmac-nt /mapuser \ /in mssql.keytab /out mssql.keytab -setpass -setupn /kvno /pass ktpass /princ MSSQLSvc/:@CONTOSO.COM /ptype KRB5_NT_PRINCIPAL /crypto aes256-sha1 /mapuser \ /in mssql.keytab /out mssql.keytab -setpass -setupn /kvno /pass ktpass /princ MSSQLSvc/:@CONTOSO.COM /ptype KRB5_NT_PRINCIPAL /crypto rc4-hmac-nt /mapuser \ /in mssql.keytab /out mssql.keytab -setpass -setupn /kvno /pass ktpass /princ @CONTOSO.COM /ptype KRB5_NT_PRINCIPAL /crypto aes256-sha1 /mapuser \ /in mssql.keytab /out mssql.keytab -setpass -setupn /kvno /pass ktpass /princ @CONTOSO.COM /ptype KRB5_NT_PRINCIPAL /crypto rc4-hmac-nt /mapuser \ /in mssql.keytab /out mssql.keytab -setpass -setupn /kvno /pass

  The commands above allow both AES and RC4 encryption ciphers for Active Directory authentication. RC4 is an older encryption cipher and if a higher degree of security is required, you can choose to create the keytab entries with only the AES encryption cipher. The last two UserName entries must be in lowercase, or the permssion authentication might fail.

  sudo chown mssql:mssql /var/opt/mssql/secrets/mssql.keytab sudo chmod 400 /var/opt/mssql/secrets/mssql.keytab 

  sudo mssql-conf set network.privilegedadaccount

  Note Only include the username and not domainname\username or username@domain. SQL Server internally adds domain name as required along with this username when used.

  sudo mssql-conf set network.kerberoskeytabfile /var/opt/mssql/secrets/mssql.keytab sudo systemctl restart mssql-server 

  Tip Optionally, disable UDP connections to the domain controller to improve performance. In many cases, UDP connections consistently fail when connecting to a domain controller, so you can set config options in /etc/krb5.conf to skip UDP calls. Edit /etc/krb5.conf and set the following options:

  /etc/krb5.conf [libdefaults] udp_preference_limit=0 

  At this point, you are ready to use Active Directory-based logins in SQL Server.

  Create Active Directory-based logins in Transact-SQL

  CREATE LOGIN [CONTOSO\user] FROM WINDOWS; 

  SELECT name FROM sys.server_principals; 

  Connect to SQL Server using Active Directory authentication

  Sign in to a client machine using your domain credentials. Now you can connect to SQL Server without reentering your password by using Active Directory authentication. If you create a login for an Active Directory group, any Active Directory user who is a member of that group can connect in the same way.

  The specific connection string parameter for clients to use Active Directory authentication depends on which driver you are using. Consider the examples in the following sections.

  sqlcmd on a domain-joined Linux client

  Sign in to a domain-joined Linux client using ssh and your domain credentials:

  ssh -l user@contoso.com client.contoso.com 

  Make sure you’ve installed the mssql-tools package, then connect using sqlcmd without specifying any credentials:

  sqlcmd -S mssql-host.contoso.com 

  Different from SQL Windows, Kerberos authentication works for local connection in SQL Linux. However, you still need to provide the FQDN of the SQL Linux host, and Active Directory authentication won’t work if you attempt to connect to . , localhost , 127.0.0.1 , etc.

  SSMS on a domain-joined Windows client

  Sign in to a domain-joined Windows client using your domain credentials. Make sure SQL Server Management Studio is installed, then connect to your SQL Server instance (for example, mssql-host.contoso.com ) by specifying Windows Authentication in the Connect to Server dialog.

  Active Directory authentication using other client drivers

  The following table describes recommendations for other client drivers:

  Client driver	Recommendation
  JDBC	Use Kerberos Integrated Authentication to Connect SQL Server.
  ODBC	Use Integrated Authentication.
  ADO.NET	Connection String Syntax.

  Additional configuration options

  If you are using third-party utilities such as PBIS, VAS, or Centrify to join the Linux host to Active Directory domain and you would like to force SQL server in using the openldap library directly, you can configure the disablesssd option with mssql-conf as follows:

  sudo mssql-conf set network.disablesssd true systemctl restart mssql-server 

  There are utilities such as realmd which set up SSSD, while other tools such as PBIS, VAS and Centrify do not setup SSSD. If the utility used to join Active Directory domain does not setup SSSD, it is recommended to configure disablesssd option to true . While it is not required as SQL Server will attempt to use SSSD for Active Directory before falling back to openldap mechanism, it would be more performant to configure it so SQL Server makes openldap calls directly bypassing the SSSD mechanism.

  If your domain controller supports LDAPS, you can force all connections from SQL Server to the domain controllers to be over LDAPS. To check your client can contact the domain controller over LDAPS, run the following bash command, ldapsearch -H ldaps://contoso.com:3269 . To set SQL Server to only use LDAPS, run the following:

  sudo mssql-conf set network.forcesecureldap true systemctl restart mssql-server 

  This will use LDAPS over SSSD if Active Directory domain join on host was done via SSSD package and disablesssd isn’t set to true. If disablesssd is set to true along with forcesecureldap being set to true, then it will use LDAPS protocol over openldap library calls made by SQL Server.

  Post SQL Server 2017 CU14

  Starting with SQL Server 2017 CU14, if SQL Server was joined to an Active Directory domain controller using third-party providers and is configured to use openldap calls for general Active Directory lookup by setting disablesssd to true, you can also use enablekdcfromkrb5 option to force SQL Server to use krb5 library for KDC lookup instead of reverse DNS lookup for KDC server.

  This may be useful for the scenario where you want to manually configure the domain controllers that SQL Server attempts to communicate with. And you use the openldap library mechanism by using the KDC list in krb5.conf.

  First, set disablesssd and enablekdcfromkrb5conf to true and then restart SQL Server:

  sudo mssql-conf set network.disablesssd true sudo mssql-conf set network.enablekdcfromkrb5conf true systemctl restart mssql-server 

  Then configure the KDC list in /etc/krb5.conf as follows:

  While it is not recommended, it is possible to use utilities, such as realmd, that set up SSSD while joining the Linux host to the domain, while configuring disablesssd to true so that SQL Server uses openldap calls instead of SSSD for Active Directory related calls.

  SQL Server login by using an FQDN (for example, CONTOSO.COM\Username ) is not supported. Use the CONTOSO\Username format.

  SQL Server logins from Domain Local groups are not supported. Use Global Security Domain groups instead.

  Next steps

  Contribute to SQL documentation

  Did you know that you can edit SQL content yourself? If you do so, not only do you help improve our documentation, but you also get credited as a contributor to the page.

  Feedback

  Submit and view feedback for

  Источник

  Читайте также:  Команда линукса открыть порт