While testing various SSO.m.c things, I found that sso.mozilla.org doesn't resolve at all. SSO isn't locked to o=com (MoCo) users, so please consider setting up a redirect from sso.m.o to sso.m.c to simplify "is it org or com" to "yes".
:jeff, any reason to not do this?
I can't think of any reason not to do it.
:andrew, is this something you can set up? Probably just a redirect from sso.mozilla.org to sso.mozilla.com
Assignee: infra → akrug
Two redirects, and an HSTS header on the latter, so that you aren't penalized for insecure redirects by the Observatory: http://sso.mozilla.org -> https://sso.mozilla.org and https://sso.mozilla.org -> https://sso.mozilla.com (with HSTS)
Please also ensure that the new sso.mozilla.org domain is added to the Observatory tracking list.
:jabba, I'd suggest the creation of a universal redirect service that follows all the web observatory guidelines. This would be a good quarter goal for someone looking to dive into serverless stuff. We manage a lot of redirects in different ways. It would be great to centralize them all. ( for the infosec accounts at the very least )
No activity in a year, and no timeline assigned. I don’t feel strongly about this request, so closing to remove it from my watchlists. Please feel free to reopen if/when ready to work on it again.
Status: NEW → RESOLVED
Last Resolved: 3 days ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.