Closed Bug 1207745 Opened 10 years ago Closed 10 years ago

Signing in with an incorrect google account at the partnerportal leaves you unable to sign in with a different account

Categories

(Release Engineering :: Release Requests, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mkaply, Assigned: mixedpuppy)

Details

I went to: https://partnerportal.paas.allizom.org/en-US/downloads/ And accidentally signed in with my google account that is not authorized. Ir gave me the error, but when I clicked "Try Again", the auth dialog popped up and disappeared and I got the same error. There was no opportunity to select a different Google account to try again.
Assignee: nobody → mixedpuppy
This is fixed now, you'll be able to see the email address you logged in with, and you'll be able to switch users. https://github.com/mozilla/partner-distro-portal/commit/81e443dac3b6d303ff81f733ac9c76874581aaac
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
This is not working for me on: https://partnerportal.paas.allizom.org/en-US/downloads/ I click "Sign in with Google to continue", a window pops up and go away and I get: Access Denied Your account does not have access to download any partner distributions. If you feel this is in error, please contact your partner representative at Mozilla. Provide them with this access id: us-east-1:ce1c8a08-9319-471a-b063-75232481de43 Try Again Try again takes me to the signin page. Incidentally, this new process seems quite problematic (especially with regards to requiring a google login) Why are we hiding partner builds behind a login? Was there a problem having them public?
Also I just tried to login with the account I gave access to (consulting@kaply.com) and it isn't working: Your account does not have access to download any partner distributions. If you feel this is in error, please contact your partner representative at Mozilla. Provide them with this access id: us-east-1:70d5856e-50eb-47ee-a9de-2d96a94f0238
Try the live site, the paas site is a dev site. https://fxpartners.mozilla.com/
Flags: needinfo?(mozilla)
(In reply to Mike Kaply [:mkaply] from comment #2) > Incidentally, this new process seems quite problematic (especially with > regards to requiring a google login) Is it because the google login, or the issue of switching accounts? > Why are we hiding partner builds behind a login? Was there a problem having > them public? We have partners that cannot have builds public until release/announcement. This gives us one system to handle all our partner accounts.
The google account requirement. You're making the assumption that everyone has a Google account. Also for our test teams, this adds another level of work trying to get the builds.
Flags: needinfo?(mozilla)
(In reply to Mike Kaply [:mkaply] from comment #6) > The google account requirement. > > You're making the assumption that everyone has a Google account. The intention is to switch over to firefox accounts in the future. > Also for > our test teams, this adds another level of work trying to get the builds. Getting a google account or something else? Did the live site work for you?
> Did the live site work for you? No, I sent you email. > Getting a google account or something else? The whole process. I'll talk to the team and make sure they have Google accounts to use. Being able to send them download links was much nicer.
Component: Custom Release Requests → Release Requests
You need to log in before you can comment on or make changes to this bug.