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/cli@1.17.0
Minor Changes
Patch Changes
@logto/connector-dingtalk-web@0.1.0
Minor Changes
@logto/phrases@1.11.0
Minor Changes
Patch Changes
e04d952: replace the i18n translated hook event label with the hook event value directly in the console
Create new account
->PostRegister
Sign in
->PostSignIn
Reset password
->PostResetPassword
@logto/schemas@1.17.0
Minor Changes
25d67f3: create a pre-configured role with Management API access when seeding the database
b5104d8: add new webhook events
We introduce a new event type
DataHook
to unlock a series of events that can be triggered by data updates (mostly Management API):DataHook events are triggered when the data associated with the event is updated via management API request or user interaction actions.
Management API triggered events
User interaction triggered events
76fd33b: support default roles for users
Patch Changes
@logto/core-kit@2.5.0
Minor Changes
0c70d65: define new
sso_identities
user claim to the userinfo endpoint responsesso_identities
user claim that will be used to store the user's SSO identities. The claim will be an array of objects with the following properties:details
: detailed user info returned from the SSO provider.issuer
: the issuer of the SSO provider.identityId
: the user id of the user in the SSO provider.identities
claim.identities
scope is requested, the newsso_identities
claim will be returned along with theidentities
claim in the userinfo endpoint response.@logto/connector-github@1.4.1
Patch Changes
c957555: fix
GET /users/emails
API requests break social sign-in flow errorPreviously, the GET /users/emails API was returning a 403 Forbidden error when the endpoint is not accessible. This will break the social sign-in flow in previous version, so we handled this error and return an empty array instead. In this way, the social sign-in flow will continue but with
userEmails
as an empty array, and should provide enough information for further investigation.@logto/create@1.17.0
Patch Changes
@logto/console@1.15.0
Minor Changes
b5104d8: add new webhook events
We introduce a new event type
DataHook
to unlock a series of events that can be triggered by data updates (mostly Management API):DataHook events are triggered when the data associated with the event is updated via management API request or user interaction actions.
Management API triggered events
User interaction triggered events
a0b1951: show version number in the topbar
76fd33b: support default roles for users
Patch Changes
e04d952: replace the i18n translated hook event label with the hook event value directly in the console
Create new account
->PostRegister
Sign in
->PostSignIn
Reset password
->PostResetPassword
558986d: update documentation reference links
c558aff: improve error handling on audit logs
user-id (deleted)
information instead.@logto/core@1.17.0
Minor Changes
b5104d8: add new webhook events
We introduce a new event type
DataHook
to unlock a series of events that can be triggered by data updates (mostly Management API):DataHook events are triggered when the data associated with the event is updated via management API request or user interaction actions.
Management API triggered events
User interaction triggered events
0c70d65: define new
sso_identities
user claim to the userinfo endpoint responsesso_identities
user claim that will be used to store the user's SSO identities. The claim will be an array of objects with the following properties:details
: detailed user info returned from the SSO provider.issuer
: the issuer of the SSO provider.identityId
: the user id of the user in the SSO provider.identities
claim.identities
scope is requested, the newsso_identities
claim will be returned along with theidentities
claim in the userinfo endpoint response.76fd33b: support default roles for users
Patch Changes
558986d: update documentation reference links
458746c: fix Microsoft EntraID OIDC SSO connector invalid authorization code response bug
expires_in
value type in number.expires_in
value type in string.expires_in
value type is number. (See v2-oauth2-auth-code-flow for reference)String type
expires_in
value is not supported by the current Microsoft EntraID OIDC connector, a invalid authorization response error will be thrown.Update the token response guard to handle both number and string type
expires_in
value. Make the SSO connector more robust.Updated dependencies [25d67f3]
Updated dependencies [e04d952]
Updated dependencies [cb1a38c]
Updated dependencies [558986d]
Updated dependencies [b5104d8]
Updated dependencies [0c70d65]
Updated dependencies [a0b1951]
Updated dependencies [07ac3e8]
Updated dependencies [c558aff]
Updated dependencies [76fd33b]
@logto/experience@1.6.2
Patch Changes
cb1a38c: show global loading icon on page relocate
This is to address the issue where the user is redirected back to the client after a successful login, but the page is not yet fully loaded. This will show a global loading icon to indicate that the page is still loading. Preventing the user from interacting with the current sign-in page and avoid page idling confusion.