Skip to content
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

Jump to bottom

user-jwts issues #42113

Closed
10 tasks done
Tracked by #34545
DamianEdwards opened this issue Jun 9, 2022 · 0 comments · Fixed by #42125
Closed
10 tasks done
Tracked by #34545

user-jwts issues #42113

DamianEdwards opened this issue Jun 9, 2022 · 0 comments · Fixed by #42125
Assignees
@captainsafia
Labels
area-commandlinetools Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI area-web-frameworks *DEPRECATED* This label is deprecated in favor of the area-mvc and area-minimal labels feature-userjwts The `dotnet user-jwts` CLI tool
Milestone
7.0-preview6

Comments

@DamianEdwards
Copy link
Member

DamianEdwards commented Jun 9, 2022 •
edited by captainsafia
Loading

  • user-jwts create should print the JWT details after creation, always including the name & compact format, and any custom values that were passed
  • user-jwts print should print the minimum JWT details including id, name, audiences, dates, custom roles/scopes/claims
  • user-jwts print should be formatted as fields, not the raw JSON storage format
  • user-jwts print seems to shows only a single audience for a token with multiple audiences
  • user-jwts throws exceptions for unrecognized command line options
  • user-jwts --name option should support an alias of -n
  • user-jwts help text for --issuer option should quote the default value of "dotnet-user-jwts" and end with a period
  • user-jwts help text for --scheme option should end with a period
  • user-jwts help text for --role option should end with a period
  • user-jwts help text for --claim option should end with a period
@DamianEdwards DamianEdwards added the feature-userjwts The `dotnet user-jwts` CLI tool label Jun 9, 2022
@captainsafia captainsafia self-assigned this Jun 9, 2022
@captainsafia captainsafia added this to the 7.0-preview6 milestone Jun 9, 2022
@captainsafia captainsafia added the area-web-frameworks *DEPRECATED* This label is deprecated in favor of the area-mvc and area-minimal labels label Jun 9, 2022
@captainsafia captainsafia mentioned this issue Jun 10, 2022
Merged
@rafikiassumani-msft rafikiassumani-msft mentioned this issue Jun 14, 2022
Closed
6 tasks
@ghost ghost locked as resolved and limited conversation to collaborators Jul 17, 2022
@amcasey amcasey added the area-commandlinetools Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI label Jun 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@captainsafia captainsafia

Labels
area-commandlinetools Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI area-web-frameworks *DEPRECATED* This label is deprecated in favor of the area-mvc and area-minimal labels feature-userjwts The `dotnet user-jwts` CLI tool
Projects
None yet
Milestone
7.0-preview6
Development

Successfully merging a pull request may close this issue.

Fix up user-jwts interactions captainsafia/aspnetcore
3 participants
@DamianEdwards @captainsafia @amcasey