Use new extensibility points for federated authentication #30
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gunndabad
force-pushed
the
use-new-auth-extn-points
branch
9 times, most recently
from
efcd976 to
dc7d6d4
Compare
gunndabad
force-pushed
the
use-new-auth-extn-points
branch
from
dc7d6d4 to
ff18c42
Compare
MrKevJoy
approved these changes
Sep 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Google have now added an extensibility point for using WIF with a custom-provided access token - googleapis/google-api-dotnet-client#3009. This PR moves to using that.
I've simplified the options classes as well as it doesn't seem to make sense having the auth config split out any more.
The auth mechanism is also auto-detected now based on the presence of environment variables (though it can be explicitly overridden).