mirror of
https://github.com/logto-io/logto.git
synced 2025-01-20 21:32:31 -05:00
chore: add changesets (#3219)
This commit is contained in:
parent
e4eb2dae49
commit
c127174128
9 changed files with 47 additions and 5 deletions
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
"@logto/core": minor
|
||||
"@logto/console": minor
|
||||
"@logto/phrase": minor
|
||||
"@logto/phrase-ui": minor
|
||||
"@logto/phrases": minor
|
||||
"@logto/phrases-ui": minor
|
||||
---
|
||||
|
||||
## Creating your social connector by SAML/OIDC/OAuth 2.0 effortlessly
|
||||
## Creating your social connector with ease
|
||||
|
||||
We’re 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.
|
||||
|
|
@ -1,5 +1,4 @@
|
|||
---
|
||||
"@logto/connector-kit": minor
|
||||
"@logto/core": minor
|
||||
---
|
||||
|
29
.changeset/good-dodos-visit.md
Normal file
29
.changeset/good-dodos-visit.md
Normal file
|
@ -0,0 +1,29 @@
|
|||
---
|
||||
"@logto/console": major
|
||||
"@logto/core": major
|
||||
"@logto/schemas": major
|
||||
---
|
||||
|
||||
**Decouple users and admins**
|
||||
|
||||
## 💥 BREAKING CHANGES 💥
|
||||
|
||||
Logto was using a single port to serve both normal users and admins, as well as the web console. While we continuously maintain a high level of security, it’ll still be great to decouple these components into two separate parts to keep data isolated and provide a flexible infrastructure.
|
||||
|
||||
From this version, Logto now listens to two ports by default, one for normal users (`3001`), and one for admins (`3002`).
|
||||
|
||||
- Nothing changed for normal users. No adaption is needed.
|
||||
- For admin users:
|
||||
- The default Admin Console URL has been changed to `http://localhost:3002/console`.
|
||||
- To change the admin port, set the environment variable `ADMIN_PORT`. For instance, `ADMIN_PORT=3456`.
|
||||
- You can specify a custom endpoint for admins by setting the environment variable `ADMIN_ENDPOINT`. For example, `ADMIN_ENDPOINT=https://admin.your-domain.com`.
|
||||
- You can now completely disable admin endpoints by setting `ADMIN_DISABLE_LOCALHOST=1` and leaving `ADMIN_ENDPOINT` unset.
|
||||
- Admin Console and admin user data are not accessible via normal user endpoints, including `localhost` and `ENDPOINT` from the environment.
|
||||
- Admin Console no longer displays audit logs of admin users. However, these logs still exist in the database, and Logto still inserts admin user logs. There is just no convenient interface to inspect them.
|
||||
- Due to the data isolation, the numbers on the dashboard may slightly decrease (admins are excluded).
|
||||
|
||||
If you are upgrading from a previous version, simply run the database alteration command as usual, and we'll take care of the rest.
|
||||
|
||||
> **Note** DID YOU KNOW
|
||||
>
|
||||
> Under the hood, we use the powerful Postgres feature Row-Level Security to isolate admin and user data.
|
14
.changeset/pink-maps-yell.md
Normal file
14
.changeset/pink-maps-yell.md
Normal file
|
@ -0,0 +1,14 @@
|
|||
---
|
||||
"@logto/core": minor
|
||||
"@logto/ui": minor
|
||||
---
|
||||
|
||||
**Customize CSS for Sign-in Experience**
|
||||
|
||||
We have put a lot of effort into improving the user sign-in experience and have provided a brand color option for the UI. However, we know that fine-tuning UI requirements can be unpredictable. While Logto is still exploring the best options for customization, we want to provide a programmatic method to unblock your development.
|
||||
|
||||
You can now use the Management API `PATCH /api/sign-in-exp` with body `{ "customCss": "arbitrary string" }` to set customized CSS for the sign-in experience. You should see the value of `customCss` attached after `<title>` of the page. If the style has a higher priority, it should be able to override.
|
||||
|
||||
> **Note**
|
||||
>
|
||||
> Since Logto uses CSS Modules, you may see a hash value in the `class` property of DOM elements (e.g. a `<div>` with `vUugRG_container`). To override these, you can use the `$=` CSS selector to match elements that end with a specified value. In this case, it should be `div[class$=container]`.
|
|
@ -7,7 +7,7 @@
|
|||
---
|
||||
|
||||
<p align="center">
|
||||
Logto is going to lauch Cloud (Preview) and OSS General Availabilty on <a href="https://www.producthunt.com/products/logto" target="_blank">Product Hunt!</a><br/>
|
||||
Logto is going to launch Cloud (Preview) and OSS General Availability on <a href="https://www.producthunt.com/products/logto" target="_blank">Product Hunt!</a><br/>
|
||||
Click the “Notify me” button on the page in order to receive a notification when our launch is live.
|
||||
</p>
|
||||
<p align="center">
|
||||
|
|
Loading…
Add table
Reference in a new issue