[Security] Bump Microsoft.AspNetCore.Authentication.JwtBearer from 3.1.6 to 5.0.8

[dependabot-preview]

Bumps Microsoft.AspNetCore.Authentication.JwtBearer from 3.1.6 to 5.0.8.

Release notes

Sourced from Microsoft.AspNetCore.Authentication.JwtBearer's releases.

.NET 5.0.8

Release

.NET 5.0.7

Release

.NET 5.0.6

Release

.NET 5.0.5

Release

.NET 5.0.4

Release

.NET 5.0.3

Release Notes Install Instructions

Repos

• Core

.NET 5.0.2

Release Notes Install Instructions

Repos

• Core

.NET 5.0.1

Release Notes Install Instructions

Repo

• Core

.NET 5

Release Notes Install Instructions

Repo

• Core

.NET 5 RC 2

Release Notes Install Instructions

... (truncated)

Commits

• ae2eaba Merge in 'release/5.0' changes
• d2eab53 Propagate repair commands to inner bundles in Hosting Bundle (#33611)
• 342fdd0 [internal/release/5.0] Update dependencies from dnceng/internal/dotnet-efcore
• 222c7a3 [internal/release/5.0] Update dependencies from dnceng/internal/dotnet-runtime
• 939ceed Merged PR 15835: [internal/release/5.0] Update dependencies from dnceng/inter...
• c791165 Merged PR 15681: [internal/release/5.0] Update dependencies from dnceng/inter...
• b89a6d3 Merge remote-tracking branch 'upstream/release/5.0' into internal/release/5.0
• cb28516 [internal/release/5.0] Update dependencies from dnceng/internal/dotnet-runtime
• 29cd71c Update dependencies from https://github.com/dotnet/arcade build 20210512.2 (#...
• 4bb1820 Merge in 'release/5.0' changes
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[sucrose0413]

@ganesanarun I encountered a similar dependency hell issue when bump Microsoft.AspNetCore.Authentication.JwtBearer from 3.1.6 to 5.0.8.
Hope the fix in #509 can help you.

Best regards,
sucrose

[dependabot-preview]

We've just been alerted that this update fixes a security vulnerability:

Sourced from The GitHub Security Advisory Database.

ASP.NET Core Information Disclosure Vulnerability

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 5.0, .NET Core 3.1 and .NET Core 2.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

An information disclosure vulnerability exists in .NET 5.0, .NET Core 3.1 and .NET Core 2.1 where a JWT token is logged if it cannot be parsed.

Patches

• If you're using .NET 5.0, you should download and install Runtime 5.0.9 or SDK 5.0.206 (for Visual Studio 2019 v16.8) or SDK 5.0.303 (for Visual Studio 2019 V16.10) from https://dotnet.microsoft.com/download/dotnet-core/5.0.

• If you're using .NET Core 3.1, you should download and install Runtime 3.1.18 or SDK 3.1.118 (for Visual Studio 2019 v16.4) or 3.1.412 (for Visual Studio 2019 v16.7 or later) from https://dotnet.microsoft.com/download/dotnet-core/3.1.

... (truncated)

Affected versions: [">= 3.0.0, < 3.1.18"]