erinstellato
Today, we can log in using a servicePrincipal, but only when paired with a client secret.
Can we look forward to logging in with a servicePrincipal using certificate-based authentication (CBA) - just as we can today using System.Data.SqlConnection or Microsoft.Data.SqlConnection?
Looking at the dialog, technically, it shouldn't take up anymore real estate than the current servicePrincipal option, if presented as an additional option in the Authentication drop-down list, since the password box could simply take the thumbprint (with the caveat that the certificate would have to be established in the appropriate per machine or per user certificate store).
It's not a big issue today that we cannot do this, however, as reluctance from security departments continues to grow for creating secrets for servicePrincipals (I'm seeing - and even advocating for this myself - today), the justification for creating a secret solely to leverage SSMS will carry diminishing weight over time.
Cheers,
Lain