-
-
Notifications
You must be signed in to change notification settings - Fork 837
Description
Verified issue does not already exist?
I have searched and found no existing issue
What error did you receive?
Even though it's throwing an error it's still creating the connection string.
Any attempt to set values for TrustServerCertificate and EncryptConnection then force the use of a credential.
Adding a value for SQLCredential causes another issue requiring ApplicationIntent to be required
Once all that is supplied we are back to the first error, but now the connection string exposes the username and password of the credential, since Integrated Security is no longer a valid option
Steps to Reproduce
New-DbaConnectionString -SqlInstance
Please confirm that you are running the most recent version of dbatools
2.1.18
Other details or mentions
No response
What PowerShell host was used when producing this error
PowerShell Core (pwsh.exe), Windows PowerShell (powershell.exe), VS Code (terminal)
PowerShell Host Version
Name Value
PSVersion 7.4.3
PSEdition Core
GitCommitId 7.4.3
OS Microsoft Windows 10.0.19045
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
SQL Server Edition and Build number
Microsoft SQL Server 2022 (RTM-CU13) (KB5036432) - 16.0.4125.3 (X64) May 1 2024 15:05:56 Copyright (C) 2022 Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2019 Standard 10.0 (Build 17763: ) (Hypervisor)
.NET Framework Version
.NET 8.0.6