Closed gdestuynder closed 7 years ago
@gene1wood @hmitsch @m-branson
This is a user-impacting change (GitHub users will see a new request for authorization), so looking for some comments - though I'd vote to just do it.
If you're curious how it looks like just login with github to https://social-ldap-pwless.testrp.security.allizom.org/
@gdestuynder The impact was light and much as expected, I'm good with implementing.
@gdestuynder how many users do we have that don't have MFA in our ORG?
@gdestuynder I'd also go for it. Maybe a short notice on the Slack #announcements channel to inform people about the user-impacting change?
and/or to the iam public mailinglist i'd say
@gdestuynder ha, excellent point ... what is the "IAM Public Mailinglist" at this point?
I currently know of these lists:
it looks like we could merge many of these iam-dev @mozilla.com can redirect to iam+internal@mozilla-community.org mozilla.dev.identity could go to iam@mozilla-community.org or does it have to stay separated?
Sorry for hijacking the conversation. I created a separate issue for mailing lists (#149).
lets depend this on #149 and I'll switch over when #149 is closed/done
communication sent to iam@mozilla-community.org
The change has been made (timestamp: this comment)
When enabled this will prompt the users using github for a new authorization: read-only access to your private profile. It needs to be enabled before we can require MFA for GitHub accounts