This repository was archived by the owner on Sep 10, 2024. It is now read-only.
v0.10.0 #3128
sandhose
announced in
Announcements
v0.10.0
#3128
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Breaking changes
Changes since
0.10.0-rc.0New features
CAPTCHA protection on the registration form
Password-based registration can now be protected with a CAPTCHA challenge. MAS supports Google’s reCAPTCHA, hCAPTCHA, as well as Cloudflare Turnstile
Email-based password recovery
When enabled, this feature allows users to recover their account, by sending a link to their confirmed email addresses.
Self-service password change
In addition to password recovery, users can change their password themselves through the new password-change interface
Admin API
Need to build administrative or automation tools for MAS? Check out the new admin API!
This replaces the GraphQL API, which is now restricted for internal use by default. If you rely on the GraphQL API through an OAuth 2.0 token, you need to set the
undocumented_oauth2_accesssetting on thegraphqllistener.Proper password complexity calculation
To make sure your users have strong-enough passwords, MAS now calculates password complexity using the popular zxcvbn algorithm. This algorithm gives a score from 0 to 4, with suggestions on how to improve the password. By default, MAS will require new passwords to have at least 3, which has a good balance between security and convenience.
This means that the parameters to set a minimum password length and require some symbols are now removed.
Rate-limiting
Some operations are more sensitive than others. You wouldn’t want someone to be able to brute force your password, would you? MAS will now rate-limit such operations, both per-IP and per account to avoid that. See the configuration documentation to learn more.
Other improvements
mas-cli config sync --pruneto apply the change. They will still be kept in the database, to avoid losing existing links.upstream_oauth2andclientssections were still required to start up. If you kept those to work around the bug in 0.9.0, you can now remove them if you don’t use them.Docker image
Regular image:
Debug variant:
syn2masmigration tool:Full list of changes (excluding dependency upgrades)
mas_graphqlcrate into themas_handlerscrate by @reivilibre in Merge themas_graphqlcrate into themas_handlerscrate #2783setPasswordGraphQL mutation for setting a user's password by @reivilibre in Add asetPasswordGraphQL mutation for setting a user's password #2820password_change_allowedtoSiteConfigby @reivilibre in GraphQL API: Addpassword_change_allowedtoSiteConfig#2857Full Changelog: v0.9.0...v0.10.0
This discussion was created from the release v0.10.0.
Beta Was this translation helpful? Give feedback.
All reactions