Skip to content

Feature/per firewall configuration#1

Merged
Spomky merged 2 commits into
mainfrom
feature/per-firewall-configuration
Jun 5, 2026
Merged

Feature/per firewall configuration#1
Spomky merged 2 commits into
mainfrom
feature/per-firewall-configuration

Conversation

@Spomky

@Spomky Spomky commented Jun 5, 2026

Copy link
Copy Markdown
Member

No description provided.

Spomky added 2 commits June 5, 2026 19:18
Drop the global `dbsc:` extension configuration entirely; every option is now
configured under the firewall's `device_bound_session` key. Each firewall gets
its own isolated service graph (algorithm provider, proof verifier, challenge
store/manager, binding repository, cookie factory, session-config factory,
handlers and controllers), built from abstract templates by the security
factory.

- Register/refresh routes are generated per firewall by a new DbscRouteLoader,
  reading the `dbsc.firewalls` parameter populated by the factory (paths default
  to /dbsc/<firewall>/{register,refresh}, overridable per firewall).
- binding_repository and challenge_store become per-firewall service-id options;
  null keeps a per-firewall in-memory store (no cross-firewall leakage).
- The profiler data collector aggregates per-firewall state via tagged service
  locators.
- Remove config/config.php and all %dbsc.*% parameters.
- Update tests, docs and the deptrac ruleset accordingly.
@Spomky Spomky merged commit 8979c4d into main Jun 5, 2026
2 checks passed
@Spomky Spomky deleted the feature/per-firewall-configuration branch June 5, 2026 17:19
@Spomky Spomky added this to the 0.1.0 milestone Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant