Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@logto/[email protected]
Patch Changes
@logto/[email protected]
Patch Changes
@logto/[email protected]
@logto/[email protected]
Minor Changes
3594e13: refactor: switch to
@logto/experience
package with latest Experience APIIn this release, we have transitioned the user sign-in experience from the legacy
@logto/experience-legacy
package to the latest@logto/experience
package. This change fully adopts our new Experience API, enhancing the underlying architecture while maintaining the same user experience.@logto/experience
package by default.API Transition: The new package leverages our latest Experience API.
Patch Changes
7b342f7: remove
client_id
from OIDC SSO connector's token request body for better compatibilityThis updates addresses an issue with client authentication methods in the token request process. Previously, the
client_id
was included in the request body while also using the authentication header for client credentials authentication.This dual method of client authentication can lead to errors with certain OIDC providers, such as Okta, which only support one authentication method at a time.
Key changes
Removal of
client_id
from request body: Theclient_id
parameter has been removed from the token request body. According to the OAuth 2.0 specification,client_id
in the body is required only for public clients.