We’re excited to announce the release of version 1.17. The 1.17 release shipped on Jun 2, 2020. This version delivers new features as well as resolving issues for users on version 1.16 and older.
FusionAuth has support for Sign in with Apple as an identity provider. You can now let your users authenticate with their Apple account.
Refresh tokens saw some improvements. You can now issue one time use refresh tokens as well as expire them based on when they were last used. This expiration policy means that if you are using refresh tokens to maintain a user session, the session can be maintained as long as the user remains active.
All identity providers now have lambdas for user data reconciliation. This allows developers complete control over how these configurations work and what information is set or written to the user object during login. The business logic has not changed, but it has been extracted from an internal FusionAuth service to a Lambda that can be modified by administrators. If you have an OIDC or SAMLv2 setup with an existing lambda, you will need to merge your logic with the extracted logic.
And of course there are 8 other bugs squashed and GitHub issues resolved as well.
Please see the release notes for the full breakdown of the changes between 1.16 and 1.17.
If you’d like to upgrade your FusionAuth instance, see our upgrade guide. If you have a licensed edition, open a support request from your account dashboard and we’ll take care of you. Or, if you’d like to download and use FusionAuth, check out your options.