0
Fork 0
mirror of https://github.com/logto-io/logto.git synced 2024-12-16 20:26:19 -05:00

chore: add changesets (#3218)

Co-authored-by: Gao Sun <gao@silverhand.io>
This commit is contained in:
Darcy Ye 2023-02-24 19:30:55 +08:00 committed by GitHub
parent be4701ac7f
commit bd3469e42f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 22 additions and 0 deletions

View file

@ -0,0 +1,12 @@
---
"@logto/core": minor
"@logto/console": minor
"@logto/phrase": minor
"@logto/phrase-ui": minor
---
## Creating your social connector by SAML/OIDC/OAuth 2.0 effortlessly
Were excited to announce that Logto now supports standard protocols (SAML, OIDC, and OAuth2.0) for creating social connectors to integrate external identity providers. Each protocol can create multiple social connectors, giving you more control over your access needs.
To simplify the process of configuring social connectors, were replacing code-edit with simple forms. SAML already supports form configuration, with other connectors coming soon. This means you dont need to compare documents or worry about code format.

View file

@ -0,0 +1,10 @@
---
"@logto/connector-kit": minor
"@logto/core": minor
---
## Enable connector method `getUserInfo` read and write access to DB
Logto connectors are designed to be stateless to the extent possible and practical, but it still has some exceptions at times.
With the recent addition of database read and write access, connectors can now store persistent information. For example, connectors can now store access tokens and refresh tokens to minimize number of requests to social vendor's APIs.