-
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
Claims cannot be deserialized #22
Comments
I have the same problem. Is there any work around how to resolve that issue? |
@vindemi I have not found any solutions for this issue. If I am not mistaken, Microsoft is working to support Our solution was to not use Claims but Roles instead. The serialization of Roles is not a problem. But soon we will move to Identity Server with SQL Server because this library is not maintained and it has this issue, also it does not support partitioning so I do not think that it is production ready. |
I'm also using IdentityServer4 and have it running fine against the `public class JsonClaimConverter : JsonConverter
I also added this to the DocumentDBUserStore for the FindBy... issues.
|
If I create a user without claims it can log in without any errors.
If I add some claims to the user upon registration then the user cannot log in.
The error is thrown when the
DocumentDbUserStore
FindByNameAsync
orFindByEmailAsync
actions try to read the user data.The problem is that the Document DB SDK does not respect the
JsonConver.DefaultSettings
. You wrote in a comment that this is a workaround but it is not the case.I forked the repository and I get the following error message:
The text was updated successfully, but these errors were encountered: