-
Notifications
You must be signed in to change notification settings - Fork 43
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
Error running application after upgrade to core 2.0 #16
Comments
Hi, I've managed to overcome this issue by creating a new JsonConverter that ignores the ClaimsPrincipal
Not sure if that was supposed to be intendent? Maybe it should not ignore the entire object, but just extract the Claims list and reconstruct the ClaimsPrincipal on Read? At least I can login using this, not sure if all features of Identity are still available. |
I tried adding a pull request with some new converters. Unsure if they will fit all scenarios though. #18 |
Hi, Apparently, the user document is being created in the DocumentDB but external logins are not being added because of the error. Thanks. |
@rafaykh90 Thanks to the PRs of @joaomatossilva and @projecteon, with the current bits this should work fine now (without any code changes on your side for now, which might change if we can't get the back compat issue discussed in #17 sorted out). I'll try to get a prerelease NuGet package out there soon, in the meantime you could download the latest bits yourself. |
A cheese workaround for JsonClaimConverter issues.
|
Hi,
I am running into a runtime error when logging in with a newly created user through:
result = await _userManager.AddLoginAsync
The same issue is mentioned here.
Any input on how to solve this or if its more deeply related to this library?
The text was updated successfully, but these errors were encountered: