support ClaimActions configure for dashboard

[WeihanLi]

Description

Try to support configure additional ClaimMap for the OpenIdConnect authentication

Fixes #7755

verified locally

usage example:

{
    "Authentication": {
        "Schemes": {
            "OpenIdConnect": {
                "Authority": "https://id.weihanli.xyz",
                "ClientId": "aspire",
                "ClientSecret": "",
                "GetClaimsFromUserInfoEndpoint": true,
                "Scope": [
                    "roles"
                ]
            }
        }
    },
    "Dashboard": {
        "Frontend": {
            "AuthMode": "OpenIdConnect",
            "OpenIdConnect": {
                "RequiredClaimType": "role",
                "RequiredClaimValue": "Aspire",
                "ClaimActions": [
                    {
                        "ClaimType": "role",
                        "JsonKey": "role"
                    }
                ]
            }
        }
    }
}

environment sample:

  - name: Dashboard__Frontend__AuthMode
    value: "OpenIdConnect"
  - name: Dashboard__Frontend__OpenIdConnect__ClaimActions_0_ClaimType
    value: "role"
  - name: Dashboard__Frontend__OpenIdConnect__ClaimActions_0_JsonKey
    value: "role"
  - name: Dashboard__Frontend__OpenIdConnect__RequiredClaimType
    value: "role"
  - name: Dashboard__Frontend__OpenIdConnect__RequiredClaimValue
    value: "Aspire"

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

[Copilot]

Pull Request Overview

This PR adds support for configuring additional ClaimActions for OpenIdConnect authentication via a new property in DashboardOptions. It enables claim action configuration through a semicolon-separated string of commands that are parsed and applied during dashboard authentication setup.

• Introduces ClaimActions configuration in DashboardOptions.
• Parses and applies ClaimActions in DashboardWebApplication.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/Aspire.Dashboard/DashboardWebApplication.cs	Adds logic to parse and apply custom ClaimActions for OpenIdConnect.
src/Aspire.Dashboard/Configuration/DashboardOptions.cs	Adds a new string property to hold the ClaimActions configuration.

[WeihanLi]

The failed test seems not related to the change

[WeihanLi]

@JamesNK could you please help have a look on this

[davidfowl]

@WeihanLi sorry for letting this go stale. This change has no tests and no scenario that we can verify (we need to be able to prevent regressions).

Do you still want this PR merged? Is so, can you figure out what tests would be best to add?

[WeihanLi]

can you figure out what tests would be best to add?

Will try to add test cases this weekend

@davidfowl thanks for the comment, great to hear some feedback

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 8396

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 8396"

[WeihanLi]

Could use JsonElement.Parse when we update to .NET 10

[JamesNK]

Merged. I made some minor clean up changes.

Thanks @WeihanLi