Closed Bug 651576 Opened 14 years ago Closed 14 years ago

Domain name for share servers

Categories

(Cloud Services :: Operations: Miscellaneous, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mixedpuppy, Unassigned)

References

Details

Prior to getting any oauth tokens, a domain name for the server should be decided. I'm assuming this would be share.mozilla.com or something similar. Some services require the ability to put a special file on the server that will be used to validate the secret keys.
Blocks: 651555
share.services.mozilla.com sound OK? We already have the *.services.mozilla.com wildcard SSL cert.
(In reply to comment #1) > share.services.mozilla.com sound OK? That looks good, lets go with it!
Cool. Shouldn't be any prep work other than adding the DNS once we're setting up in production. stage will be stage-share.services.mozilla.com.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
if you have different domain names for staging and production you will need two sets of oauth keys since they are tied to the domain name
hmm, more info...we currently have separate domain names for staging and production, using separate oauth keys. Today we discussed using a single domain name, and using paths to separate different systems. That would allow for a single set of keys. However, I think staging might be fine for having its own set of keys.
Yeah. The plan was to have a set of keys for staging and for prod.
You need to log in before you can comment on or make changes to this bug.