Disables Integrated Security in the ConnectionString when using SQL hosting integrations.

[danm-de]

Disables the Integrated Windows Authentication when using Aspire.Hosting.SqlServer & Aspire.Hosting.Azure.Sql hosting integrations.

• adds the Integrated Security=false parameter to the ConnectionString.

Description

Kerberos/Integrated Windows authentication is typically used in corporate environments. The SQL Management Studio remembers the last (successful) connection setting. As a developer, if I copy the connection string into the "Additional Connection Settings" tab and then click "Connect", I get an error message:

The additional parameter Integrated Security=false ensures that the SQL Management Studio uses the correct connection settings (authentication using username & password). The same probably applies to AzureSqlServer - but I couldn't test that.

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes (adapted the previous/existing tests)
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No - I assume that the hosting image (and the connection string) will only be used in development and test environments.
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

[davidfowl]

cc @IEvangelist