config option reputationService.host must be able to accept a FQDN value

[jrgm]

1. In stage/production, the tigerblood endpoint is set up to use an ELB. ELB's advertise multiple IP's and those IP's can change at anytime.

2. Current master of ip-reputation-js-client, not yet published to npm, hardcodes the scheme to https, which cannot be used with IP addresses.

[jrgm]

See also mozilla-services/ip-reputation-js-client#3, where the client should be strictSSL and not follow any redirects. (Not directly related to this bug, but both this repo and that repo need to align).

[vbudhram]

Spoke with @g-k and he said that he was working on some patches for this, possibly sending the service url instead.

Connects with mozilla-services/ip-reputation-js-client#3 and mozilla-services/ip-reputation-js-client#4

[g-k]

ugh, yeah.

The package is published: https://www.npmjs.com/package/ip-reputation-js-client.

If mozilla-services/ip-reputation-js-client#4 addresses mozilla-services/ip-reputation-js-client#3, then I need to:

• publish a new major version (constructor options changed)
• update package.json (and shrinkwrap?) on https://github.com/mozilla/fxa-customs-server/compare/master...g-k:fix-rep-service-config?expand=1 (edit: now #172)
• update the stage and prod fxa puppet config mozilla-services/puppet-config#2490
  • remove fxa::auth_customs_server::reputation_service_ip
  • add fxa::auth_customs_server::reputation_service_base_url set tohttps://tigerblood.{stage|prod}.mozaws.net
  • re-enable in stage (revert mozilla-services/puppet-config#2476)

[vladikoff]

This was corrected...