This document describes changes between each past release.
- Nothing changed yet.
Optimization
- Try to keep
OAuthClient
around longer to take advantage of HTTP keepalives (#133).
Bug fixes
- Fix the
process-account-events
script to take client user ID suffixes into account (fixes #61)
- Set up metrics on the
process-account-events
script (#57). - Set up logging on the
kinto_fxa.scripts
programs (#58).
- Introduce new
kinto_fxa.scripts
. Right now the only script available isprocess-account-events
, which listens to an SQS queue for user delete events and deletes data from that user's default bucket, in order to comply with GDPR.
- Move kinto-fxa to the Kinto github org. (#54)
- Add support for multiple FxA Clients (#52)
Bug fixes
- Make sure that caching of token verification nevers prevents from authenticating requests (see mozilla/PyFxA#48)
Internal changes
- Migrate schemas to Cornice 2 #38
New features
- Improve FxA error messages (fixes #1)
Bug fixes
- Optimize authentication policy to avoid validating the token several times per request (fixes #33)
Internal changes
- Use Service from kinto.core (fixes #28)
- Make sure it does not catch Cornice 2 dependency (#36)
- Add the plugin version in the capability.
Breaking changes
- Project renamed to Kinto-fxa to match the rename of
cliquet
tokinto.core
. - Update to
kinto.core
for compatibility with Kinto 3.0. This release is no longer compatible with Kinto < 3.0, please upgrade! - With Kinto > 2.12*, the setting
multiauth.policy.fxa.use
must now be explicitly set tokinto_fxa.authentication.FxAOAuthAuthenticationPolicy
Bug fixes
- Fix checking of
Authorization
header when python is ran-O
(ref mozilla-services/cliquet#592)
- Updated to Cliquet 2.9.0
Breaking changes
- cliquet-fxa cannot be included using
pyramid.includes
setting. Usecliquet.includes
instead.
Bug fixes
- In case the Oauth dance is interrupted, return a
408 Request Timeout
error instead of the401 Unauthenticated
one. (#11) - Do not call
cliquet.load_default_settings
from cliquet-fxa (#12)
- Separate multiple scopes by a + in login URL.
Bug fixes
- Multiple scopes can be requested on the login flow.
- Multiple scopes can be required for the app.
Configuration changes
fxa-oauth.scope
is now deprecated.fxa-oauth.requested_scope
andfxa-oauth.required_scope
should be used instead.
- Add default settings to define a policy "fxa".
It is now possible to just include
cliquet_fxa
and addfxa
tomultiauth.policies
setting list. - Do not check presence of cliquet cache in initialization phase.
- Do not use Cliquet logger to prevent initialization errors.
- Do not prefix authenticated user with
fxa_
anymore (#5)
- Imported code from Cliquet