ceb97458d4
fix: correct the kind definition in the Device extension ( #6222 )
...
#### What type of PR is this?
/area core
/kind bug
/milestone 2.17.x
#### What this PR does / why we need it:
修复 Device 模型中，Kind 定义错误的问题。
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/6221
#### Does this PR introduce a user-facing change?
```release-note
None
```
2024-07-01 03:05:16 +00:00
f0445f4e51
refactor: remove page cache feature ( #6108 )
...
#### What type of PR is this?
/area core
/kind api-change
/milestone 2.17.x
#### What this PR does / why we need it:
移除内置的页面静态缓存功能，后续将由 https://github.com/halo-sigs/plugin-page-cache 插件提供。
#### Which issue(s) this PR fixes:
Fixes #5639
#### Special notes for your reviewer:
#### Does this PR introduce a user-facing change?
```release-note
移除内置的页面静态缓存功能，后续由 https://github.com/halo-sigs/plugin-page-cache 插件提供。
```
2024-06-28 10:08:59 +00:00
632bb69dfe
Refactor search engine and improve document extensibility ( #6082 )
...
#### What type of PR is this?
/kind improvement
/kind api-change
/area core
#### What this PR does / why we need it:
See https://github.com/JohnNiang/halo/blob/refactor/search/docs/extension-points/search-engine.md for more
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/5202
Fixes https://github.com/halo-dev/halo/issues/5339
Fixes https://github.com/halo-dev/halo/issues/5613
Fixes https://github.com/halo-dev/halo/issues/5172
Fixes https://github.com/halo-dev/halo/issues/4796
Fixes https://github.com/halo-dev/halo/issues/5625
Fixes https://github.com/halo-dev/halo/issues/5805
#### Special notes for your reviewer:
#### Does this PR introduce a user-facing change?
```release-note
重构搜索引擎并提高可扩展性。
```
2024-06-26 15:22:51 +00:00
8d71fc3966
feat: add device management mechanism
2024-06-26 18:52:32 +08:00
ae6724a2b6
feat: implement persistent token based remember me mechanism ( #6131 )
...
#### What type of PR is this?
/kind feature
/area core
/milestone 2.17.x
#### What this PR does / why we need it:
新增基于持久化 Token 的 RememberMe 机制
本次更新引入了一种新的 RememberMe 机制，该机制基于持久化 Token，以增强安全性和管理灵活性。在此之前，RememberMe 功能通过以下方式生成 Token，并将其作为 cookie 发送回客户端：
```
username + ":" + expiryTime + ":" + algorithmName + ":"
+ algorithmHex(username + ":" + expiryTime + ":" + password + ":" + key)
```
此方法的优点在于无需存储 Token 就可以进行验证，并且用户密码的更改会自动使 Token 失效。然而，它的主要缺点是缺乏管理能力，例如无法手动撤销 Token。
鉴于最新的设备管理需求（见 PR #6100），我们需要一种支持设备撤销（revoke）的机制。因此，我们采用了持久化 Token 的方式，并通过随机生成的方法来提高安全性，而不将用户名和密码直接签名在 Token 中。新的 Token 格式如下：
```
base64(tokenValue:series)
```
此更改将为系统带来更高的安全保障和更灵活的管理选项，特别是在需要高度控制和监管设备访问时。
#### Does this PR introduce a user-facing change?
```release-note
引入基于持久化 Token 的新 RememberMe 机制以增强安全性和管理灵活性，升级后需要重新登录
```
2024-06-26 08:40:49 +00:00
ecc0a70249
Refactor api client using separated OpenAPI groups
2024-06-25 12:31:25 +08:00
Ryan Wang