This patch removes flow based performance metrics on Payments server. The
data from the logs are not present in Redshift due to the lack of a log
pipeline to ingest and process the events. Furthermore, there was a bug
with the timing values.
This will be followed up with a switch to statsd, so that performance
metrics will be separated from flow events.
Convert the `complete_sign_up` tests to be the `verification reminders`
tests. The only flow that sends signup verification links now are the
reminders, so re-purposing this module seemed appropriate.
Not attached to an issue.
Before this signing in to an OAuth RP with a cached unverified account
would send the user to /confirm, which would have resent verification
links.
This converts that flow to use codes instead.
fixes#3649
Because:
* The stock Sentry plugin has limitations on what details it filters
from the error details.
* We've customized Hapi error reporting Sentry for auth-server and have
not used those elsewhere.
This commit:
* Brings over the Hapi Sentry configuration used in auth-server that
filters out additional PII such as uid's.
* Add's a new SQS Sentry configuration that capatures additional Sentry
details for SQS processing failures.
Closes#3422
Connects to #2427
Removes most references to the older token code route. This was the first version of the code which was supposed to replace confirmation links. It was a randomly generated code with an expiration of 20mins.
This code has been replaced with a time based code that is used for verifying a login and session.
While writing the functional test deep dive, I found myself thinking
it odd I had to explain that two files had to be included to create
a user. So I decided to make it so one file needed to be included
by exposing all TestHelper methods in FunctionalHelpers.
Not attached to an issue.
ref https://github.com/mozilla/ecosystem-platform/pull/47
While writing docs on how to ensure metrics are flushed before
FxA closes, I realized we could probably automate this. Any
time we send a notice to the browser, flush metrics first.
issue #3213
Only handles signin that requires password with unverified account,
does not handle cached signin with an unverified account or visiting
settings with an unverified account.
fixes#3459
Because:
* Metrics events for the sync-optional flow currently have a missing
`service` attribute.
* The sync-optional flow does not learn the client_id of the
connecting application until it receives the `fxa_status` message.
This commit:
* Explicitly sets the `service` attribute on the metrics object
when handling the `fxa_status` message response.
Fixes#3611.