|
|
1ddf83b28d
|
BREAKING CHANGE(vpn): replace tag-based VPN access control with source and target profiles
|
2026-04-05 00:37:37 +00:00 |
|
|
|
96d215fc66
|
feat(routes): add TLS configuration controls for route create and edit flows
|
2026-04-04 21:23:16 +00:00 |
|
|
|
c8f19cf783
|
fix(route-management): include stored VPN routes in domain resolution and align programmatic route types with dcrouter configs
|
2026-04-04 19:29:49 +00:00 |
|
|
|
ffcc35be64
|
fix(config-ui): handle missing HTTP/3 config safely and standardize overview section headings
|
2026-04-04 19:03:11 +00:00 |
|
|
|
73a47e5a97
|
fix(route-config): sync applied routes to remote ingress manager after route updates
|
2026-04-02 16:26:24 +00:00 |
|
|
|
55699f6618
|
feat(config): add reusable security profiles and network targets with route reference resolution
|
2026-04-02 15:44:36 +00:00 |
|
|
|
bb6c26484d
|
BREAKING CHANGE(db): replace StorageManager and CacheDb with a unified smartdata-backed database layer
|
2026-03-31 15:31:16 +00:00 |
|
|
|
0d9e6a4925
|
fix(config): correct VPN mandatory flag default handling in route config manager
|
2026-03-31 11:51:45 +00:00 |
|
|
|
29687670e8
|
feat(vpn): support optional non-mandatory VPN route access and align route config with enabled semantics
|
2026-03-31 11:19:29 +00:00 |
|
|
|
1e4b9997f4
|
fix(routing): apply VPN route allowlists dynamically after VPN clients load
|
2026-03-31 04:15:51 +00:00 |
|
|
|
eb211348d2
|
feat(vpn): add tag-based VPN route access control and support configured initial VPN clients
|
2026-03-30 12:07:58 +00:00 |
|
|
|
6f72e4fdbc
|
feat(vpn): add VPN server management and route-based VPN access control
|
2026-03-30 08:15:09 +00:00 |
|
|
|
c7de3873d8
|
feat(http3): add automatic HTTP/3 route augmentation for qualifying HTTPS routes
|
2026-03-19 19:06:15 +00:00 |
|
|
|
f5028ffb60
|
feat(route-management): add programmatic route management API with API tokens and admin UI
|
2026-02-23 12:40:26 +00:00 |
|
