PoC: Federated SPN Credentials #835
Merged
Conversation
This file contains 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
tehcrashxor
force-pushed
the
users/tehcrash/2404/AdoSpnFederation
branch
from
bc14e5c to
e80722c
Compare
|
@tehcrashxor - Is OIDC coming to Power Platform Actions as well? |
|
Love it 🔥🔥 |
petrochuk
approved these changes
Apr 26, 2024
petrochuk
approved these changes
Apr 26, 2024
petrochuk
approved these changes
May 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
NB: Requires not-yet published version of PAC CLI
Adds support for using Federated Credentials / Workload Identity -- allowing SPNs to use Federated Credentials to authenticate without the need for Client Secrets or Client Certificates being specified in ADO