Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

The default OIDC handler ignores updates to user emails #13277

Closed
squahtx opened this issue Jul 14, 2022 · 1 comment
Closed

The default OIDC handler ignores updates to user emails #13277

squahtx opened this issue Jul 14, 2022 · 1 comment
Labels
A-Login A-SSO Single Sign-On (maybe OIDC) P4 (OBSOLETE: use S- labels.) Okay backlog: will not schedule, will accept patches S-Minor Blocks non-critical functionality, workarounds exist. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues.

Comments

@squahtx
Copy link
Contributor

squahtx commented Jul 14, 2022

I can add some detail about this. My issue is slighty different but I think not enough to open a new one:

User information from OIDC is only fetch at the initial user creation and never again. If you add the email_template to the user_mapping_provider later existing users will not be updated. If a users email changes this change is never reflected. If you set the log level of the sso and oidc handler and log in with existing and new accounts it's clearly visible that user information is only fetched and successfully stored with the initial user creation.

Originally posted by @loelkes in #12605 (comment)


Note that user emails are stored in user_threepids, with medium='email'.

@squahtx squahtx added A-SSO Single Sign-On (maybe OIDC) S-Minor Blocks non-critical functionality, workarounds exist. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. P4 (OBSOLETE: use S- labels.) Okay backlog: will not schedule, will accept patches A-Login labels Jul 14, 2022
@clokep
Copy link
Member

clokep commented Jul 14, 2022

I think this is essentially a duplicate of #5763.

@clokep clokep closed this as completed Jul 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Login A-SSO Single Sign-On (maybe OIDC) P4 (OBSOLETE: use S- labels.) Okay backlog: will not schedule, will accept patches S-Minor Blocks non-critical functionality, workarounds exist. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
Projects
None yet
Development

No branches or pull requests

2 participants