1133891 - sso.mozilla.org does not resolve

Status: RESOLVED INCOMPLETE

Description

[Atoll R. Soderberg [:atoll, :rsoderberg]]

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".

Comment 1

[Justin Dow [:jabba]]

:jeff, any reason to not do this?

Comment 2

[Jeff Bryner [:jeff] (use NEEDINFO 😉)]

I can't think of any reason not to do it.

Comment 3

[Justin Dow [:jabba]]

:andrew, is this something you can set up? Probably just a redirect from sso.mozilla.org to sso.mozilla.com

Comment 4

[Atoll R. Soderberg [:atoll, :rsoderberg]]

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)

Comment 5

[Atoll R. Soderberg [:atoll, :rsoderberg]]

Please also ensure that the new sso.mozilla.org domain is added to the Observatory tracking list.

Comment 6

[Andrew Krug [:andrew]]

: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 )

Comment 7

[Atoll R. Soderberg [:atoll, :rsoderberg]]

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.