Announcing FusionAuth 1.40

We’re excited to announce the release of FusionAuth version 1.40.0. It shipped on Sep 16, 2022. This release includes native windows installation, Okta SCIM support for deactivation of users, and a change to how you can install the MySQL driver, as well as other bug fixes.

There are a number of new features, enhancements, and bug fixes. As always, please see the release notes for a full breakdown of the changes between 1.39 and 1.40, including any schema changes.

There were 6 issues, enhancements, and bug fixes included in this release. Read more about all the changes in the release notes.

While this was a smaller release, are a couple of changes worth calling out.

Native Windows installs

In version 1.37, we removed our native Windows installation support. We figured that people installing on Windows would be able to use the Windows Subsystem for Linux and use our Debian or RPM packages.

We were wrong. Sorry about that!

Our community and customers let us know that they needed native windows installation and that the WSL option was not workable for everyone.

As of this release, FusionAuth can be installed on Windows just as it was pre 1.37.

Enhanced SCIM support

The SCIM support in FusionAuth continues to improve. With this release, deactivation of users works with Okta systems.

In particular, Okta updates users via PUT or PATCH, setting active to false when they are deactivated.

As of this release, receiving this message from a SCIM client will deactivate the user in FusionAuth.

MySQL database driver download changes

If you are using MySQL or plan to use MySQL as the database for your FusionAuth installation, you will need to manually download the JDBC connector and place it in the correct location of your FusionAuth installation. This is required for FusionAuth to connect to any MySQL database.

If you are using PostgreSQL, this change does not affect you.

See the installation guide for additional information and instructions.

We apologize in advance for any inconvenience this causes you. Unfortunately, the Oracle GPL licensing makes it difficult for FusionAuth to easily deliver the JDBC driver, requiring this action on your part.

Upgrade at will

The release notes are a guide to the changes, fixes, and new features. Please read them carefully to see if any features you use have been modified or enhanced.

If you’d like to upgrade your self-hosted FusionAuth instance, see our upgrade guide.

If you have a FusionAuth Cloud deployment, proceed to the “Deployments” tab on your account dashboard and upgrade your instances. If you have any questions about the upgrade, please open a support ticket.

Or, if we’ve piqued your interest and you’d like to use FusionAuth, check out your options.

*** This is a Security Bloggers Network syndicated blog from The FusionAuth Blog authored by The FusionAuth Blog. Read the original post at: