Expose SqlAuthenticationParameters on SSPIContextProvider

[twsouthwick]

This change updates the SSPI context provider to surface information to implementers via SqlAuthenticationParameters.

This also expands #2559 to loop through all SPNs in the base SSPIContextProvider rather than just a specific implementation.

Part of #2253

[codecov]

Codecov Report

Attention: Patch coverage is 83.33333% with 7 lines in your changes missing coverage. Please review.

Project coverage is 66.09%. Comparing base (1e59b88) to head (72f1c99).
Report is 7 commits behind head on main.

Files with missing lines	Patch %	Lines
...crosoft/Data/SqlClient/SSPI/SSPIContextProvider.cs	83.87%	5 Missing ⚠️
...t/Data/SqlClient/SSPI/NativeSSPIContextProvider.cs	66.66%	1 Missing ⚠️
...ata/SqlClient/SSPI/NegotiateSSPIContextProvider.cs	87.50%	1 Missing ⚠️

❗ There is a different number of reports uploaded between BASE (1e59b88) and HEAD (72f1c99). Click for more details.

HEAD has 1 upload less than BASE

Flag	BASE (1e59b88)	HEAD (72f1c99)
addons	1	0

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2454      +/-   ##
==========================================
- Coverage   72.58%   66.09%   -6.49%     
==========================================
  Files         289      282       -7     
  Lines       59503    59309     -194     
==========================================
- Hits        43188    39199    -3989     
- Misses      16315    20110    +3795     

Flag	Coverage Δ
addons	?
netcore	68.88% <75.00%> (-6.24%)	⬇️
netfx	65.02% <65.62%> (-6.19%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[twsouthwick]

@mdaigle next step for sspi :)

[twsouthwick]

ping @mdaigle @cheenamalhotra

[mdaigle]

Hey @twsouthwick, I'll try to take a look at this today!

[twsouthwick]

The errors appear to also be on main and are an "Access denied" for something related to certificates. It doesn't appear to be caused by my change, but let me know if you believe it is.

[mdaigle]

I think this all makes sense to me. I'll take another look tomorrow and also see why the tests are failing.

[mdaigle]

Tests should be green now. We had a build agent issue that was resolved yesterday.

[mdaigle]

I'm trying to think of the best way to populate this. In other usage, I see serverSpn getting set as the resource and dataSource getting set as the serverName. I think it makes sense to continue that pattern here given that serverName and server SPN may be different.

[mdaigle]

SqlClient/src/Microsoft.Data.SqlClient/netcore/src/Microsoft/Data/SqlClient/SqlInternalConnectionTds.cs

Line 2437 in e0fa87b

var authParamsBuilder = new SqlAuthenticationParameters.Builder(

[mdaigle]

I'm also not sure how to feel about authority. In federated auth, it's assumed that authority will be present, but here we don't set a value.

Let me chat with the team to see if we'd prefer to create a new type to better represent this set of credentials.

[twsouthwick]

Sounds good. I refactored the builder so that the same pattern can be had wherever it's used if we want to use the existing SqlAuthenticationParameters