Support O DateTime(Offset) format in dotnet user-jwts tool

[martincostello]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

When using the new dotnet user-jwts tool, users may paste formatted date times in from other sources (e.g. decoding another existing JWT using something like jwt.io).

Describe the solution you'd like

To make copy-paste in these scenarios, supporting the "O" format would make the tool more user-friendly.

The tool already supports 4 different possible formats:

aspnetcore/src/Tools/dotnet-user-jwts/src/Commands/CreateCommand.cs

Line 14 in 6b2e422

"yyyy-MM-dd", "yyyy-MM-dd HH:mm", "yyyy/MM/dd", "yyyy/MM/dd HH:mm" };

It displays the values in "O" format from the list command, so would support round-tripping when decoded.

aspnetcore/src/Tools/dotnet-user-jwts/src/Commands/ListCommand.cs

Lines 55 to 62 in 6b2e422

	if (showTokens)
	{
	table.AddRow(jwt.Id, jwt.Scheme, jwt.Audience, jwt.Issued.ToString("O"), jwt.Expires.ToString("O"), jwt.Token);
	}
	else
	{
	table.AddRow(jwt.Id, jwt.Scheme, jwt.Audience, jwt.Issued.ToString("O"), jwt.Expires.ToString("O"));
	}

Additional context

See #41956 (comment).

/cc @DamianEdwards

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.