The file may look something like this:Ĭom.Krb5LoginModule required This is the JAAS configuration file that the MSSQL JDBC driver will consume upon server startup to provide appropriate authentication information. JAAS: After the nf file has been setup and the keytab obtained, you'll need to create a file named nf and place it inside your $ARTIFACTORY_HOME/etc directory. Note: Make sure the user that is running Artifactory can read the keytab file. In most cases, the principal in the keytab will be mapped to the Active Directory Service Account that you’re using to access the Linux machine and run processes with it. The keytab may already exist somewhere on your system but, if it doesn't, you’ll need to obtain it from a Windows/KDC administrator who can generate one for your machine. Keytab: When necessary (i.e., when there is no ticket in the cache or when a ticket has expired), the MSSQL JDBC driver will use a keytab file to obtain a TGT from the KDC. Note: Make sure the user that is running your Artifactory process can read the /etc/nf file. All configuration options can be found HERE.
SQL SERVER CONNECTION STRING WINDOWS AUTHENTICATION HOW TO
JFrog can provide basic guidance on how to do this, but the ones who will know best how to create a nf file that is suitable for your environment and uses the right options are your Windows/Unix administrators. It's possible that your machine already has this file in /etc/nf.
Krb.conf: First, you'll need to make sure the nf file exists on your system and is properly configured to use the Kerberos realm on which your MSSQL server resides. The setup process for Linux users is somewhat more complicated: On a Windows machine, it might be as simple as placing the sqljdbc_auth.dll in your system path and specifying integratedSecurity=true on the JDBC connection string. You can set up the MSSQL JDBC driver to authenticate against your MSSQL database using Kerberos authentication.