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.

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

[Feature Request] Automated testing for mixed versions of IM in ASP.NET #2944

Open
keegan-caruso opened this issue Oct 25, 2024 · 0 comments
Labels
Dependency Mismatch Transitive dependency might be at play and create issues resulting in incorrect versions of a class Internal Indicates issue was opened by the IdentityModel team P1 More important, prioritize highly

Comments

@keegan-caruso
Copy link
Contributor

keegan-caruso commented Oct 25, 2024

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

It is clear that many customers will mix and match versions of Identity Model, for example:

Create a new webapi with JWT Bearer which takes a dep on OpenIdConnect:
Microsoft.IdentityModel.Protocols.OpenIdConnect

The app then will update a different dependency, say Microsoft.IdentityModel.Tokens, to a higher version.

Describe the solution you'd like

Automated testing that is essentially

dotnet new webapi --auth singleorg --clientid <client-id> --tenant-id <tenant-id>
dotnet add package Microsoft.IdentityModel.Tokens --version <version-under-test>
<run-test-that-validates-a-token-and-parses-claims>

Describe alternatives you've considered

There is not a good alternative, this is a scenario that should be supported, it needs to be tested.

Additional context
See all the issues tagged with dependency mismatch

@keegan-caruso keegan-caruso added P1 More important, prioritize highly Internal Indicates issue was opened by the IdentityModel team Dependency Mismatch Transitive dependency might be at play and create issues resulting in incorrect versions of a class labels Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dependency Mismatch Transitive dependency might be at play and create issues resulting in incorrect versions of a class Internal Indicates issue was opened by the IdentityModel team P1 More important, prioritize highly
Projects
None yet
Development

No branches or pull requests

1 participant