we want to be able to connect to SQL server from ArcGIS pro using NTLM authentication. Right now, there is no option to select NTLM

[KannanSundaresan]

make NTLM as option that we can choose while making SQL server connection from ArcGIS pro. Right now only AD authentication is supported but ArcGIS server running in Linux cannot connect to SQL server without kerberos ticket renewal every 15 mins.

[MarceloMarques]

NOTES

Using NTLM authentication to connect to SQL Server - JDBC Driver for SQL Server | Microsoft Learn

Understanding Kerberos and NTLM authentication in SQL Server Connections - Microsoft Community Hub

kerberos - Why is MS SQL Server Using NTLM Authentication? - Server Fault

Using Kerberos Configuration Manager for SQL Server - SQL Server | Microsoft Learn

Using Kerberos integrated authentication to connect to SQL Server - JDBC Driver for SQL Server | Mic...

[KannanSundaresan]

Kerberos authentication on ArcGIS server in Linux is not supported by ESRI. So we thought of using NTLM  so that we have some security rather than no security. 

[MarceloMarques]

@KannanSundaresan - an alternative is to use SQL Server Connections with SSL Certificate for encryption and security, see link below to the SQL Server documentation. I hope this helps.

Configure SQL Server Database Engine for encryption - SQL Server | Microsoft Learn
Certificate requirements for SQL Server - SQL Server | Microsoft Learn
Configure client computer and application for encryption - SQL Server | Microsoft Learn

[SSWoodward]

NTLM has been replaced by Kerberos.  There are currently no plans to support NTLM in future releases of ArcGIS Pro. 

[KannanSundaresan]

if that is the case, can ESRI give us a solution to connect to SQL server from ArcGIS server (Linux) using Kerberos. Kerberos uses tickets which expires in certain period of time and we have renew it manually using a script and we need to run the script in background. This is not reliable in Production environment.

[KannanSundaresan]

@MarceloMarques  we are using encryption. but our Security team insist using active directory authentication and avoid using local DB user authentication. hence we need to migrate from local user to AD user.