Compare commits
6 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
| 128083aee6 | |||
| f59f987115 | |||
| 71e8c09e8f | |||
| acc61a4c3d | |||
| 67f62276e7 | |||
| 6ef12408df |
@@ -10,6 +10,46 @@ for what changed inside the apps it composes.
|
|||||||
|
|
||||||
## [Unreleased]
|
## [Unreleased]
|
||||||
|
|
||||||
|
## [1.7.0] - 2026-07-27
|
||||||
|
|
||||||
|
### Bumped
|
||||||
|
- sso-manager-node -> [v1.5.1](https://github.com/theta42/sso-manager-node/releases/tag/v1.5.1)
|
||||||
|
- jump-host -> [v1.5.0](https://github.com/theta42/jump-host/releases/tag/v1.5.0)
|
||||||
|
|
||||||
|
Two production bugs fixed: `PUT /api/user/:uid` 500'd with an LDAP
|
||||||
|
`ObjectClassViolationError` when setting `sshPublicKey` on any account
|
||||||
|
predating the `ldapPublicKey` objectClass (notably the bootstrap admin) —
|
||||||
|
and the exact same bug, in the shared `@simpleworkjs/ldap` package's
|
||||||
|
`addSshKey`, was silently aborting SSH connections at jump-host's
|
||||||
|
key-injection step for the same class of accounts. Both are fixed by
|
||||||
|
ensuring the objectClass is present before writing the attribute. Also
|
||||||
|
fixed: the Directory's "add resource" modal left the parent-Service
|
||||||
|
dropdown blank when adding an OAuth Integration.
|
||||||
|
|
||||||
|
Jump-host's web dashboard also gained a "Hosts you can reach" list
|
||||||
|
(admins see "All hosts") — previously it only showed usage metrics with
|
||||||
|
no way to see your actual access from the browser.
|
||||||
|
|
||||||
|
No `setup.sh`, compose, or config change.
|
||||||
|
|
||||||
|
## [1.6.0] - 2026-07-26
|
||||||
|
|
||||||
|
### Bumped
|
||||||
|
- jump-host -> [v1.4.0](https://github.com/theta42/jump-host/releases/tag/v1.4.0)
|
||||||
|
|
||||||
|
Jump-host gains **standalone mode**: it can now run with no LDAP directory and
|
||||||
|
no SSO Manager at all, storing users and hosts itself via
|
||||||
|
`@simpleworkjs/orm` (Sequelize; SQLite by default, any Sequelize-supported
|
||||||
|
dialect). This is an app-internal capability, opt-in via
|
||||||
|
`standalone.enabled` in jump-host's own config — the bundled theta-env stack
|
||||||
|
is unaffected and continues to wire jump-host to the shared LDAP directory
|
||||||
|
and SSO Manager as before. Two bugs were also fixed in jump-host's SSH
|
||||||
|
server: an ephemeral listen port (`0`) was silently overridden back to the
|
||||||
|
default, and session listeners could miss a client's immediate `exec`/`shell`
|
||||||
|
request.
|
||||||
|
|
||||||
|
No `setup.sh`, compose, or config change on the theta-env side.
|
||||||
|
|
||||||
## [1.5.0] - 2026-07-26
|
## [1.5.0] - 2026-07-26
|
||||||
|
|
||||||
### Bumped
|
### Bumped
|
||||||
|
|||||||
Binary file not shown.
|
After Width: | Height: | Size: 83 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 394 KiB After Width: | Height: | Size: 310 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 232 KiB After Width: | Height: | Size: 141 KiB |
@@ -25,6 +25,7 @@ The SSO Manager and the proxy it fronts, both stood up by one `./setup.sh` run:
|
|||||||
|
|
||||||
<a href="images/sso-dashboard.png" target="_blank"><img src="images/sso-dashboard.png" alt="SSO Manager dashboard" width="49%"></a>
|
<a href="images/sso-dashboard.png" target="_blank"><img src="images/sso-dashboard.png" alt="SSO Manager dashboard" width="49%"></a>
|
||||||
<a href="images/proxy-hosts.png" target="_blank"><img src="images/proxy-hosts.png" alt="Proxy host list" width="49%"></a>
|
<a href="images/proxy-hosts.png" target="_blank"><img src="images/proxy-hosts.png" alt="Proxy host list" width="49%"></a>
|
||||||
|
<a href="images/jump-dashboard.png" target="_blank"><img src="images/jump-dashboard.png" alt="Jump Host dashboard" width="49%"></a>
|
||||||
|
|
||||||
*(click either screenshot to view full size)*
|
*(click either screenshot to view full size)*
|
||||||
|
|
||||||
|
|||||||
+1
-1
Submodule jump-host updated: 9db530565d...fd863b89ca
+1
-1
Submodule sso-manager-node updated: 59ae30897b...5665504bc1
Reference in New Issue
Block a user