You are viewing limited content. For full access, please sign in.

Question

Question

Can you use a Windows Account for the SQL Connection when using the Deployment Toolkit?

asked on March 17 Show version history

When configuring the global SQL connection in the json file can you use a Windows Account for the SQL Username value?

I have tested with a Windows Account that has been added to SQL Server with the sysadmin role, but received the following error:

[xxx.xxx.com]: 03/17/2021 12:52:24 (UTC-04:00) - Validate product settingsWrite-ErrorLog : [xxx.xxx.com]: 03/17/2021 12:52:25 (UTC-04:00) - Test SQL connection failed on DirectoryServer-11.0.0 when connecting to database server
xxx.xxx.com using xxxxxx\xxxxxx with error: Exception calling "Open" with "0" argument(s): "Login failed for user 'xxxxx\xxxxx'."
At C:\LaserficheDeploymentToolkit\Scripts\CommonFunction\HelperFunction.ps1:152 char:9
+         Write-ErrorLog "Test SQL connection failed on $AppName when c ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-ErrorLog

Exception calling "Open" with "0" argument(s): "Login failed for user 'xxxxx\xxxxx'."
At C:\LaserficheDeploymentToolkit\Scripts\CommonFunction\HelperFunction.ps1:143 char:9
+         $sqlConnection.Open();
+         ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : SqlException

It works correctly if I use a SQL user instead.

1 0

Replies

replied on March 31 Show version history

Thanks for reporting this, Blake. For now, we only support use a SQL user for the SQL Connection as it uses SQL user to create databases by default when configuring products

We may consider supporting this feature later.

    

1 0
replied on March 31

@████████, thank you for the reply. It is best practice to use Windows Accounts to run the services and therefore also to communicate with SQL, so it would make sense to update the Deployment Toolkit to allow for the ability to set the service accounts to Windows Accounts and then set the SQL connection to use Windows Authentication.

Without this, we have to go back to each application and reconfigure it after the Deployment Toolkit has finished.

 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.