Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

Non-nullable property 'id' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'authenticationRequest' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'jwtRequest' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

Non-nullable property 'Challenge' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Message' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'authenticationValidation' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'displayName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'description' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.