Deprecate verification at persona.org or browserid.org

mozilla / identity-ops

Tools and Chef cookbooks used by Mozilla Services Operations to provision and manage Persona

Other

24 stars 12 forks source link

Deprecate verification at persona.org or browserid.org #63

Closed gene1wood closed 10 years ago

gene1wood commented 11 years ago

Change persona.org and browserid.org to dynect driven redirects to subdomains

relud commented 10 years ago

closing: won't fix, because persona.org and browserid.org are now running on route53, not dynect, and route53 does not support this. Instead we will be modifying persona.org to resolve to the persona webhead elb, and having nginx on the webheads serve up redirects as needed.

fmarier commented 10 years ago

Two other factors to consider:

a lot of notice has been given about us cutting these off
many libraries got patched last year

So we may not need to maintain these redirects anymore.

gene1wood commented 10 years ago

@fmarier could you tell us what to look for in the logs to determine if the existing requirements for these zones (e.g. serving up include.js, proxying verify puts, etc) are no longer needed?

I know that eyedee.me still uses https://browserid.org/include.js

fmarier commented 10 years ago

This ticket was about the verifier, I would leave the include.js redirects in place.

What you should look for is anybody POSTing to browserid.org/verify or persona.org/verify.