[Feature Request] Automated testing for mixed versions of IM in ASP.NET #2944
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
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
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
The text was updated successfully, but these errors were encountered: