search

hassanakbar4 / mailarchive-tickets

0 stars 0 forks source link

Review archive login and private list membership functionality #324

Open hassanakbar4 opened 3 years ago

hassanakbar4 commented 3 years ago

component_MailArchive: User Interface type_task | by rcross@amsl.com

Background:

So, most User objects in mail archive had username=[django user (an email address)], email=‘’. The default implementation of mozilla_django_oidc locates users my matching User email with email from user info returned by the OIDC Provider. Copying username to email resolved the issue. New User objects created by mozilla_django_oidc have both attributes set.

settings.py:OIDC_USERINFO = 'ietf.ietfauth.utils.openid_userinfo' settings.py:OIDC_EXTRA_SCOPE_CLAIMS = 'ietf.ietfauth.utils.OidcExtraScopeClaims'

Issue migrated from trac:3265 at 2021-09-22 16:58:18 +0500

hassanakbar4 commented 3 years ago

@hassanakbar4 changed title from Ensure archive uses Datatracker primary email for list membership checks to Review archive login and private list membership functionality

hassanakbar4 commented 3 years ago

@hassanakbar4 changed status from new to accepted

hassanakbar4 commented 3 years ago

@hassanakbar4 commented

John Scudder reported no access to private lists. After logging in via OpenID / Datatracker he sees primary email as login name in upper right, not DT login. This user in mail archive is not associated with any private lists, as that association is made with only the DT login address. Archive logins need to revert to DT login, not primary email, to restore functionality.