Release Notes > 6.4.13
Webiny 6.4.13 Changelog
See what's new in Webiny version 6.4.13
Admin
Stricter Identity Provider Token Verification (#6282
)
The API now applies stricter checks to the identity provider tokens (JWT) it receives. The Admin app already sends the right token, so this only affects custom clients that call the API with a token they obtained themselves.
- Cognito: only ID tokens are accepted. A Cognito access token is now rejected.
- Auth0 and Okta: the token must be issued by the configured issuer and for the configured client ID. This is the case for the ID token of your Webiny application, while access tokens issued for another audience and tokens issued for another application are rejected.
- Signing algorithm: only tokens signed with
RS256are accepted.
If your own client sends an access token in the Authorization header, change it to send the ID token instead. Otherwise its requests are no longer authenticated after the upgrade.
Headless CMS
Stricter Validation of thefieldsArgument in GenericcmsQueries and Mutations (#6282
)
The fields argument of the generic cms operations (getEntry, listEntries, createEntry, updateEntryRevision, publishEntryRevision and unpublishEntryRevision) now accepts only field paths made of field names separated by dots, for example id or values.author.name. Each name can contain only letters, digits and underscores, and cannot start with a digit. Any other value returns an error instead of the entry, so if you pass anything else in fields, change it to plain field paths.
Development
Updated Dependencies (#6282
)
Routine dependency updates, including @aws-sdk/*, @rspack/core, type-fest, debounce and minimatch.