Scope source for the request transformer #36302
Merged
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.
Fixes #36301
Tom, Wade ... I just need one review to get this in.
This will improve the article to match updates made to the BWA+Entra+BFF sample apps (9.0 and 10.0) that I made as part of placing new 10.0 samples this morning. Specifically ...
Programfile. [Note: Halter specifically wants hardcoded security config for the base case sample.] I updated the samples to read the scopes from aList<string>in theProgramfile to match how other security config is established. This PR mirrors the sample update in the article with an added instruction on configuring the server project with the scope(s).Note in passing that Copilot is asking for more context, but this is an advanced article for advanced devs. We don't need to bog down the article with what Copilot is asking for. Besides, this article will be up for more work in '26 if I can get time to work on the Blazor security node next year. I might flesh out some of this with additional remarks ... but not now ... I'm 🏃♂️😅 to get everything in place for 10.0 GA.
Internal previews