-
Notifications
You must be signed in to change notification settings - Fork 4k
Microsoft.IdentityModel.Tokens problem in beta4 #141
Comments
Noticed it was the same problem in Samples when I opened them. So to reproduces , just open |
Open our MVC and API sample and compare. let me know |
@leastprivilege yes I did and got the same problem :)
|
The Credential verb changed. But that is trivial. This is less so: error CS1705: Assembly 'IdentityServer4' with identity 'IdentityServer4, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' uses 'Microsoft.IdentityModel.Tokens, Version=5.0.0.699, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'Microsoft.IdentityModel.Tokens' with identity 'Microsoft.IdentityModel.Tokens, Version=5.0.0.127, Culture=neutral, PublicKeyToken=31bf3856ad364e35' Is it possible that the beta4 package was built against that one "preview versions" nuget server that Microsoft has set up so it either directly or indirectly floats a Microsoft.IdentityModel.Tokens that is newer than the newly released 5.0.0 version? |
having a look |
https://www.nuget.org/packages/System.IdentityModel.Tokens.Jwt/ not sure where you have that nuget from - it is def not from us. Maybe delete your .vs folder and nuget cache |
Tried that also but no luck. The nuget comes from https://www.nuget.org/packages/System.IdentityModel.Tokens.Jwt/ cause it has an dependency on it. |
FWIW that error is not a nuget error. It's a dll reference error. So it could be that System.IdentityModel.Tokens.Jwt has a package dependency on the correct package but a dll dependency on the wrong dll... If System.IdentityMode.Tokens.Jwt was in fact the package built (as in compiled) using a nuget repo other than the public one we all use... or just a local cache that used to. ... that said - deleting package cache does no good As a workaround, we just commented out setting up the certificate for now as we haven't gotten far enough along down the IdentityServer4 path for it to matter yet. Hopefully things will be worked out in the next few days. |
I'm getting the same thing. I just installed 2015 Fresh w/ Update 3 & The 1.0.0 Preview 2 SDK. I created an empty Core WebApp and when I started to pull from the example...got the same error. |
Same problem here. |
same issue here |
Got the same problem as well. This looks like a bug. |
OK - after deleting my package cache I can repro the problem. Not sure yet what the problem is. working on it. |
I published beta4-update1 - give it a try |
It works, thanks! |
thanks |
What a quick fix! Thanks. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hey ,
Just tried out beta4. But getting this error:
my project.json looks like this:
so not sure why I'm getting that error.
The text was updated successfully, but these errors were encountered: