Because:
* The /devices route only uses information from the auth-server db.
* OAuth devices may have more up-to-date information in the oauth db.
This commit:
* Adds a lookup to the oauth db when calculatig the list of devices.
Because:
* The new Settings page needs an alert-style bar to display messages to users.
This commit:
* Creates an AlertBar component in fxa-settings and places it in the correct DOM location
* Moves shared hooks with Modal into hooks.tsx
* Adds titles to AlertBar/Modal close buttons per content strategy request
* Removes 'transition:desktop' class in AppLayout because it canceled out position:fixed Nav functionality
fixes#4929
When a password change is required the lockedAt flag is set, currently by an external script. Until the password is changed all sessions for such an account must be verified. The 'password-change' verificationReason is returned in the response to tell the frontend to show the change password ui. The resetAccount db procedure resets the lockedAt value to null when the password is changed.
fix(customs): Fix undefined errors when blocking a request from ip service
fix(customs): don't try to write records from reputationService to memcache
fix(customs): Call setRecord instead of setRecords
fix(logs): Emit statsd errnos
feat(auth): changed handling of logins
fix(customs): flag emails in customs server blocking
Because:
- a survey should be displayed above other content
This commit:
- set a z-index for the survey that's higher than others in the content server
Because:
* We want to require batches of users to change their password.
* The graphql-api package has easy access to the auth database for
update statements.
This commit:
* Add's a must-change-password script that will batch larger update
commands to quickly set the lockedAt flag used to determine if the
user needs to change their password.
Closes#5592
Because:
* The main content layout was missing a class and the nav fixed width didn't render properly with long strings.
This commit:
* Adds 'w-full' class to the Nav/main container and 'transform' class to the nav container.
Because:
- we want to be able to use a user's language(s) to determine survey
eligibility
This commit:
- compare the configured languages in the browser against a list of
configured for a survey
Because:
- we want to limit a survey to a certain percentage of visitors
This commit:
- use the rate value from a survey's configuration in the process that
determines whether the visitor should receive a survey
- supply both cents and currency values for every price to be formatted
in emails based on user locale
- remove `$` currency symbol from all strings tagged for l10n in email
templates
- normalize on `paymentProrated` across emails for prorated payment (was
`proratedAmount` in some spots)
- tweak `acceptedLanguage` in email tests, which ended up exposing an
unexpected issue during development
fixes#5450
Danny Coates
Lauren Zugai
Ryan Kelly
Edouard Oger
Jody Heavener
Vijay Budhram
Shubham Kumar
Barry Chen
Vijay Budhram
Ben Bangert
Vlad Filippov
Les Orchard