Skip to content

Merge to Live #35074

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Mar 28, 2025
Merged

Merge to Live #35074

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f8a16d3
Add PAR support configuration (#35073)
guardrex Mar 27, 2025
5ad952e
remove broken link
timdeschryver Mar 27, 2025
9d5a2a6
remove Di parents, add Br parents (#35077)
BillWagner Mar 28, 2025
20e0c85
Merge pull request #35076 from timdeschryver/issue/35046
Rick-Anderson Mar 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions aspnetcore/blazor/security/blazor-web-app-with-oidc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,6 +80,16 @@ If using Visual Studio, you can confirm the secret is set by right-clicking the

The following <xref:Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectOptions> configuration is found in the project's `Program` file on the call to <xref:Microsoft.Extensions.DependencyInjection.OpenIdConnectExtensions.AddOpenIdConnect%2A>:

:::moniker range=">= aspnetcore-9.0"

* <xref:Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectOptions.PushedAuthorizationBehavior%2A>: Controls [Pushed Authorization Requests (PAR) support](xref:aspnetcore-9#openidconnecthandler-adds-support-for-pushed-authorization-requests-par). By default, the setting is to use PAR if the identity provider's discovery document (usually found at `.well-known/openid-configuration`) advertises support for PAR. If you wish to require PAR support for the app, you can assign a value of [`PushedAuthorizationBehavior.Require`](xref:Microsoft.AspNetCore.Authentication.OpenIdConnect.PushedAuthorizationBehavior). PAR isn't supported by Microsoft Entra, and there are no plans for Entra to ever support it in the future.

```csharp
oidcOptions.PushedAuthorizationBehavior = PushedAuthorizationBehavior.UseIfAvailable;
```

:::moniker-end

* <xref:Microsoft.AspNetCore.Builder.RemoteAuthenticationOptions.SignInScheme%2A>: Sets the authentication scheme corresponding to the middleware responsible of persisting user's identity after a successful authentication. The OIDC handler needs to use a sign-in scheme that's capable of persisting user credentials across requests. The following line is present merely for demonstration purposes. If omitted, <xref:Microsoft.AspNetCore.Authentication.AuthenticationOptions.DefaultSignInScheme%2A> is used as a fallback value.

```csharp
Expand Down Expand Up @@ -305,6 +315,16 @@ If using Visual Studio, you can confirm the secret is set by right-clicking the

The following <xref:Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectOptions> configuration is found in the project's `Program` file on the call to <xref:Microsoft.Extensions.DependencyInjection.OpenIdConnectExtensions.AddOpenIdConnect%2A>:

:::moniker range=">= aspnetcore-9.0"

* <xref:Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectOptions.PushedAuthorizationBehavior%2A>: Controls [Pushed Authorization Requests (PAR) support](xref:aspnetcore-9#openidconnecthandler-adds-support-for-pushed-authorization-requests-par). By default, the setting is to use PAR if the identity provider's discovery document (usually found at `.well-known/openid-configuration`) advertises support for PAR. If you wish to require PAR support for the app, you can assign a value of [`PushedAuthorizationBehavior.Require`](xref:Microsoft.AspNetCore.Authentication.OpenIdConnect.PushedAuthorizationBehavior). PAR isn't supported by Microsoft Entra, and there are no plans for Entra to ever support it in the future.

```csharp
oidcOptions.PushedAuthorizationBehavior = PushedAuthorizationBehavior.UseIfAvailable;
```

:::moniker-end

* <xref:Microsoft.AspNetCore.Builder.RemoteAuthenticationOptions.SignInScheme%2A>: Sets the authentication scheme corresponding to the middleware responsible of persisting user's identity after a successful authentication. The OIDC handler needs to use a sign-in scheme that's capable of persisting user credentials across requests. The following line is present merely for demonstration purposes. If omitted, <xref:Microsoft.AspNetCore.Authentication.AuthenticationOptions.DefaultSignInScheme%2A> is used as a fallback value.

```csharp
Expand Down Expand Up @@ -520,6 +540,16 @@ If using Visual Studio, you can confirm the secret is set by right-clicking the

The following <xref:Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectOptions> configuration is found in the project's `Program` file on the call to <xref:Microsoft.Extensions.DependencyInjection.OpenIdConnectExtensions.AddOpenIdConnect%2A>:

:::moniker range=">= aspnetcore-9.0"

* <xref:Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectOptions.PushedAuthorizationBehavior%2A>: Controls [Pushed Authorization Requests (PAR) support](xref:aspnetcore-9#openidconnecthandler-adds-support-for-pushed-authorization-requests-par). By default, the setting is to use PAR if the identity provider's discovery document (usually found at `.well-known/openid-configuration`) advertises support for PAR. If you wish to require PAR support for the app, you can assign a value of [`PushedAuthorizationBehavior.Require`](xref:Microsoft.AspNetCore.Authentication.OpenIdConnect.PushedAuthorizationBehavior). PAR isn't supported by Microsoft Entra, and there are no plans for Entra to ever support it in the future.

```csharp
oidcOptions.PushedAuthorizationBehavior = PushedAuthorizationBehavior.UseIfAvailable;
```

:::moniker-end

* <xref:Microsoft.AspNetCore.Builder.RemoteAuthenticationOptions.SignInScheme%2A>: Sets the authentication scheme corresponding to the middleware responsible of persisting user's identity after a successful authentication. The OIDC handler needs to use a sign-in scheme that's capable of persisting user credentials across requests. The following line is present merely for demonstration purposes. If omitted, <xref:Microsoft.AspNetCore.Authentication.AuthenticationOptions.DefaultSignInScheme%2A> is used as a fallback value.

```csharp
Expand Down
3 changes: 0 additions & 3 deletions aspnetcore/tutorials/first-web-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -769,9 +769,6 @@ There are many other tools that can be used to test web APIs, for example:
* [curl](https://terminalcheatsheet.com/guides/curl-rest-api). Swagger uses `curl` and shows the `curl` commands it submits.
* [Fiddler](https://www.telerik.com/fiddler)

For more information, see:

* [Install and test APIs with `http-repl`](xref:tutorials/first-web-api?view=aspnetcore-6.0&preserve-view=true#ihr6)

<!-- Verify https://go.microsoft.com/fwlink/?linkid=2123754 goes to this H2. Verify the latest released version is on top so this anchor works -->
<a name="over-post"></a>
Expand Down
1 change: 0 additions & 1 deletion aspnetcore/tutorials/first-web-api/includes/first-web-api7.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -457,7 +457,6 @@ There are many other tools that can be used to test web APIs, for example:
For more information, see:

* [Minimal API tutorial: test with .http files and Endpoints Explorer](xref:tutorials/min-web-api)
* [Install and test APIs with `http-repl`](xref:tutorials/first-web-api?view=aspnetcore-6.0&preserve-view=true#ihr6)

<!-- Verify https://go.microsoft.com/fwlink/?linkid=2123754 goes to this H2. Verify the latest released version is on top so this anchor works -->
<a name="over-post"></a>
Expand Down
1 change: 0 additions & 1 deletion aspnetcore/tutorials/first-web-api/includes/first-web-api8.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -413,7 +413,6 @@ There are many other tools that can be used to test web APIs, for example:
For more information, see:

* [Minimal API tutorial: test with .http files and Endpoints Explorer](xref:tutorials/min-web-api)
* [Install and test APIs with `http-repl`](xref:tutorials/first-web-api?view=aspnetcore-6.0&preserve-view=true#ihr6)

<!-- Verify https://go.microsoft.com/fwlink/?linkid=2123754 goes to this H2. Verify the latest released version is on top so this anchor works -->
<a name="over-post"></a>
Expand Down
46 changes: 3 additions & 43 deletions quest-config.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,51 +37,11 @@
"ParentNodeId": 308205
},
{
"Label": "okr-freshness",
"Semester": "Dilithium",
"ParentNodeId": 237266
},
{
"Label": "okr-curation",
"Semester": "Dilithium",
"ParentNodeId": 237271
},
{
"Label": "user-feedback",
"Semester": "Dilithium",
"ParentNodeId": 233465
},
{
"Label": "okr-health",
"Semester": "Dilithium",
"ParentNodeId": 237266
},
{
"Label": "doc-bug",
"Semester": "Dilithium",
"ParentNodeId": 233465
},
{
"Label": "sfi-ropc",
"Semester": "Dilithium",
"ParentNodeId": 271716
},
{
"Label": "sfi-admin",
"Semester": "Dilithium",
"ParentNodeId": 271716
},
{
"Label": "sfi-images",
"Semester": "Dilithium",
"ParentNodeId": 286370
},
{
"Semester": "Dilithium",
"ParentNodeId": 227486
"Semester": "Bromine",
"ParentNodeId": 403735
}
],
"DefaultParentNode": 308205,
"DefaultParentNode": 403735,
"WorkItemTags": [
{
"Label": "9.0",
Expand Down
Loading