Skip to content
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

Infra work for bulletproof Apple account usage #1492

Closed
autonome opened this issue May 6, 2020 · 7 comments
Closed

Infra work for bulletproof Apple account usage #1492

autonome opened this issue May 6, 2020 · 7 comments
Assignees
Labels
area/macos MacOS effort/weeks Estimated to take multiple weeks kind/bug A bug in existing code (including security flaws) kind/maintenance Work required to avoid breaking changes or harm to project's status quo P0 Critical: Tackled by core team ASAP status/blocked Unable to be worked further until needs are met

Comments

@autonome
Copy link
Contributor

autonome commented May 6, 2020

Recommendation from Andrew Schwab after confirming Twilio numbers are detected:

  • Create a Google Group (I'd recommend something like ipfs-apple-id@)
  • Create an Apple ID with that group email
  • Document the Apple ID email login and reset question in 1Password in a shared vault
  • Setup the phones for members of the group for SMS 2FA
  • Add a note in 1Password indicating whose phones are currently connected

So we need to determine if we need to create new Apple ID or switch existing account @olizilla has created to use the new email alias.

From my previous iOS work, I think it depends on how @olizilla set the account up. A real pain to move stuff between accounts, and accounts have a lot of personal detail and config (at least in the US).

@autonome autonome added the need/triage Needs initial labeling and prioritization label May 6, 2020
@jessicaschilling jessicaschilling added effort/days Estimated to take multiple days, but less than a week kind/bug A bug in existing code (including security flaws) P0 Critical: Tackled by core team ASAP status/ready Ready to be worked and removed need/triage Needs initial labeling and prioritization labels May 7, 2020
@jessicaschilling
Copy link
Contributor

@rafaelramalho19 -- can you please prioritize this over the loading indicator work? Thank you!

@rafaelramalho19
Copy link
Contributor

I've followed the steps but apparently there was a problem creating the account in the last steps 😕

image

@andyschwab
Copy link
Member

Followup: looking into solving this using Apple Developer Program for Organizations capabilities.

@lidel lidel added area/macos MacOS effort/weeks Estimated to take multiple weeks kind/maintenance Work required to avoid breaking changes or harm to project's status quo status/in-progress In progress and removed effort/days Estimated to take multiple days, but less than a week status/ready Ready to be worked labels May 18, 2020
@jessicaschilling
Copy link
Contributor

@andyschwab -- just checking in on what you've learned? Thanks!

@andyschwab
Copy link
Member

andyschwab commented May 28, 2020

@jessicaschilling - identified a solid path forward, but currently on hold until we can use the best account to setup a Developer Program Organization and update permissions accordingly. I'll continue to track this and action as soon as it is unblocked.

@jessicaschilling
Copy link
Contributor

Awesome, thanks @andyschwab! I'll move out of our in-progress queue until you tell me otherwise.

@jessicaschilling jessicaschilling added status/blocked Unable to be worked further until needs are met and removed status/in-progress In progress labels May 28, 2020
@lidel
Copy link
Member

lidel commented Oct 9, 2020

I believe this is done, I was able to use my own account to inspect stuff under our Org when I migrated new secrets from Travis to Github Actions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/macos MacOS effort/weeks Estimated to take multiple weeks kind/bug A bug in existing code (including security flaws) kind/maintenance Work required to avoid breaking changes or harm to project's status quo P0 Critical: Tackled by core team ASAP status/blocked Unable to be worked further until needs are met
Projects
None yet
Development

No branches or pull requests

5 participants