Windows Authentication and the Tentacles Used in Deployment

Legacy Execution
1

Continuing the discussion from Unable to connect to SQL Server via Windows Authentication even when tenticle is running as domain user:

I’m interested in learning what the actual fix was here. We’re having the same issue and it’s not returning relevant information for correction. Please be forthright here.

2

Hi Erik,

Thanks for getting in touch.

Could you provide some more information about what your issue is?

Are you trying to connect to a database as part of a deployment and you are getting the Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. error? If that is the case, are you able to log in as the Tentacle user and connect to the SQL Server using that connection string?

Can you also let me know what version of Octopus you are running and what version of SQL Server you are trying to connect to?

Thank you and best regards,
Henrik

3

Correct on all parts there, there’s a piece of the process that needs to connect to a SQL Server database utilizing Integrated Security. The User assigned to the Tentacle Service has proper access and has been tested to connect and execute said scripts against said database(s). But we get this Unrusted error. We are using version 4.1.9

4

Hi Erik,

Thanks for the extra information.

Is your Tentacle running in a different domain to your SQL Server? If they are, is there a trust setup between the two domains?

Can you send through the connection string you are using.

And, can you try the solution in this blog post and see if that resolves your connection issue.

Thank you and best regards,
Henrik

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.