fix: prevent prisma crash on OIDC accounts with non-standard fields#708
Open
mikimandoki wants to merge 1 commit into
Open
fix: prevent prisma crash on OIDC accounts with non-standard fields#708mikimandoki wants to merge 1 commit into
mikimandoki wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Kanidm includes an
issued_token_typefield in its token response which isn't in the Prisma schema, causing a DB crash before the account could be created. Rather than adding another provider-specific case tolinkAccount, this PR replaces the entire chain with a generic sanitisation pass usingPrisma.AccountScalarFieldEnumas the source of truth. Any provider with non-standard fields now works without further changes.Checklist
CONTRIBUTING.mdin its entiretySee #682