For Windows installation,
shutdownApplicationsManager.bat
shutdownApplicationsManager.bat -force
For Linux installation,
shutdownApplicationsManager.sh
shutdownApplicationsManager.sh-force
![]()
SQLJDBCDriver {
com.sun.security.auth.module.Krb5LoginModule required
useticketCache=false
doNotPrompt=true
usekeytab=true
keytab="C://Users//kerberosuser.MSSQLKERBEROS//Desktop//kerberos//AppManager14//working//conf//KerberosConfigurations//MSSQL//krb5.keytab"
principal="MSSQLSvc/mssql-kerberos-dc1.mssqlkerberos.com:1433@MSSQLKERBEROS.COM"
storeKey=false
debug=false;
};
6. To use ticket cache for Kerberos authentication,
![]()
SQLJDBCDriver {
com.sun.security.auth.module.Krb5LoginModule required
useticketCache=true
ticketCache="C://Users//kerberosuser.MSSQLKERBEROS//Desktop//kerberos//AppManager14//working//conf//KerberosConfigurations//MSSQL//krb5cc_kerberosuser"
doNotPrompt=true
usekeytab=false
principal="kerberosuser@MSSQLKERBEROS.COM"
storeKey=false
debug=false;
};
![]()
SQLJDBCDriver {
com.sun.security.auth.module.Krb5LoginModule required
useticketCache=false
doNotPrompt=false
usekeytab=false
principal="MSSQLSvc/mssql-kerberos-dc1.mssqlkerberos.com:1433@MSSQLKERBEROS.COM"
storeKey=false
debug=true;
};
Add the below entry after this line,
For example: login.config.url.1=file:C:/Users/kerberosuser.MSSQLKERBEROS/Desktop/kerberos/AppManager14/working/conf/KerberosConfigurations/MSSQL/MicrosoftJDBCDriver/login.conf
10. Now start Applications Manager and verify that Kerberos authentication is being used by executing the following query on the SQL Server. The value returned in the auth_scheme column should be KERBEROS.
(or)