-
Notifications
You must be signed in to change notification settings - Fork 76
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
Table Structure Miss match #4
Comments
I tried to migrate from IdentityServer4 version 3.1.3 to version 4.0.4 and faced the same problems. Apparently there was a class restructuring, and this affects directly the database table structure. Please inform if you managed to migrate from the original code in the tutorial (https://deblokt.com/2020/01/24/02-identityserver4-entityframework-net-core-3-1/) to a new updated code compliant with IS4 version 4.0.x. Thanks. |
I did the tutorial using IS 4.0.4, I was able to figure everything out. I had to check some of the IdentityServer4 4.0.4 code and samples on github, though, Two Entity classes in ConfigurationDbContext.ClientSeed that gave me problems were IdentityClaim -> IdentityResourceClaim (this class is a drop-in replacement) and ApiScope.ResourceId -> ApiResourceScope (use this class to associate the ApiScope to an ApiResource) |
Yeah, it would be nice for them to make another walkthrough for IS 4.x, and specifically say what version of IdentityServer they are using. The link on the first page of the walkthrough at https://deblokt.com/2020/01/24/01-identityserver4-quickstart-net-core-3-1/ went to the "latest" IdentityServer docs, which this solution definitely doesn't cover the database changes. |
Dear Deblokt,
Thank you very much for writing such a wonderful tutorial. While following the tutorials (https://deblokt.com/2020/01/24/02-identityserver4-entityframework-net-core-3-1/) , step by step I encountered Table Structure miss match and extra tables, which further created issues for seeding the data. I would like to request you kindly share some pointers to solve this issue.
For reference,
regards,
Gopal Chettri
The text was updated successfully, but these errors were encountered: