# MSSQL Integrated security from a docker container

**URL:** <https://forum.inductiveautomation.com/t/mssql-integrated-security-from-a-docker-container/64660>\
**Category:** Ignition\
**Tags:** database, docker\
**Created:** [September 29, 2022, 2:41pm UTC](https://forum.inductiveautomation.com/t/mssql-integrated-security-from-a-docker-container/64660 "2022-09-29T14:41:04Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![declan.mccarthy](https://avatars.discourse-cdn.com/v4/letter/d/dec6dc/32.png) [@declan.mccarthy](https://forum.inductiveautomation.com/u/declan.mccarthy)\
**Post date:** [January 23, 2023, 3:06pm UTC](https://forum.inductiveautomation.com/t/mssql-integrated-security-from-a-docker-container/64660/3 "2023-01-23T15:06:30Z")

</div>

So this is a lot less complicated than first thought  
Set up your SQL server with the correct SPNs and constrained delegation as you would do for any form of kerberos connection  
The MS SQL jdbc driver can connect directly without needing any kerberos setup on the linux host or container  
Username should be entered as username@REALM  
The Extra Connection properties should include "integratedSecurity=true;authenticationScheme=JavaKerberos"

On a linux/container env, the username must include the realm, on windows its optional  
On a windows env, the ignition service needs to be started with the same username that you use to connect to SQL, on linux the default installation can be used.

---

_[View the full topic](https://forum.inductiveautomation.com/t/mssql-integrated-security-from-a-docker-container/64660)._