Release Notes > 5.41.1
Webiny 5.41.1 Changelog
See what's new in Webiny version 5.41.1
release on GitHub.Security
External Identity Providers - Roles and Teams Assignments (#4349]
We’ve addressed a couple of issues related to assigning roles when using external identity providers, like Auth0 or Okta. We’ve also added one new feature. More information can be found below.
1.groupsProperty Now Works as Expected
Prior to this release, when using external identity providers, assigning roles via the newly introduced groups property would not work. For example, with Auth0, the following configuration would not work:
With this release, this has been addressed and both group and groups properties can now be used to assign roles when using external identity providers.
As mentioned in the 5.41.0 release notes, the group property has been deprecated. Users are encouraged to use the groups property instead.
2. Programmatically Created Roles Now Work as Expected
When using external identity providers, trying to assign a role to a user that was programmatically created would not work. This has now been addressed.
Programmatic creation of roles and teams has been introduced in the 5.41.0 release.
3. Ability to Assign Teams (#4349]
Since the introduction of the Teams feature, users were not able to assign teams to users when using external identity providers. With this release, this gap has finally been closed.
Note that the Teams feature is part of Webiny’s enterprise offering. To learn more, please check out the Teams article.
Page Builder
New "Website" Extension (#4344)
With the new Page Builder element extension, we’ve also introduced the new Website extension, which makes it easier to start extending Webiny’s Website application.
As already mentioned above, in the same fashion, the extension can be accessed via the webiny scaffold, or the new webiny extension command.
At the moment, there aren’t any code examples that include the new Website extension. We’ll be adding them in the upcoming releases.
Development
Improved Error Messages (#4341)
Prior to this release, in case a user immediately tried to watch the Admin or Website frontend applications, but the Core and API applications weren’t deployed, they would receive an error message that wasn’t very helpful. We’ve improved this error message to provide more context and help users understand what’s going on.
Thewebiny extensionCommand
Up until now, in order to scaffold a new extension, users had to run the yarn webiny scaffold command, and then select New Extension from the list of all available scaffolds. And although this isn’t a big deal, still, since extensions are becoming more and more important in the last couple of releases, we’ve decided to introduce a new command called webiny extension.
Essentially, everything stays the same, but now, instead of running yarn webiny scaffold, users can run yarn webiny extension to scaffold a new extension.
Note that the webiny scaffold command will still work, but moving forward, we’ll be emphasizing the use of the new webiny extension command.