Closed Bug 1588639 Opened 5 years ago Closed 5 years ago

Please set up SSO for FirefoxCI Taskcluster instaqnce

Categories

(Infrastructure & Operations :: SSO: Requests, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: edunham, Unassigned)

References

Details

Later this week I'll be setting up the FirefoxCI Taskcluster instance. I will need to provision it with SSO login credentials.

Your service name, URL and a service owner, in order to know whom to send the credentials to and what the service is about.

Service name: FirefoxCI Taskcluster.

URL will be https://firefox-ci-tc.services.mozilla.com

Service owner: Me, edunham@mozilla.com.

We ask about the amount of expected users for load and licensing reasons - this helps us ensure you get a good quality of service.

User base should be comparable to current taskcluster.net, for which I believe Mozilla SSO is already configured. This work is part of an eventual migration off of taskcluster.net and onto https://firefox-ci-tc.services.mozilla.com.

We need a callback URL (also called redirect URI or recipient) parameter.

https://firefox-ci-tc.services.mozilla.com/login/mozilla-auth0/callback

Production, stage or dev.

This is production.

Who should be allowed to log in? All Moco/Mofo/Pocket/Mozilla Online staff? Moco only? A specific LDAP group? A specific mozillians.org group? Everyone, including random people on the internet? NDA only, plus staff? etc.

Please make this the same as the current taskcluster.net SSO configs.

This is now blocking us from standing up the FirefoxCI Taskcluster. Please let me know what if anything I can do to help expedite it.

Blocks: 1573897
Flags: needinfo?(jdow)

I've created the integration and e-mailed the gpg-encrypted credentials. I've set up access control here: https://github.com/mozilla-iam/sso-dashboard-configuration/pull/328/commits/46c6c44bac7d669ad102980e1a72f0107fb9ec5e but that is not deployed live yet, it's pending peer review.

Flags: needinfo?(jdow)

Thank you!

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.