Spring

Before you start

A firewall integration enforces the signed policy bundle of your site in front of your origin: block, redirect, challenge and token-gated routes. It fetches the bundle from GET /v1/policies/<site key>, verifies its signature offline and decides every request the same way in every language. It does not replace verifying tokens in your own code. A request that reaches your origin another way (a direct IP, another hostname, a path the integration was not installed on) is never evaluated, so let only the integration reach the origin. See firewall policies.

The secret key (rgsk_...) is needed only for requireToken rules. Without it such a rule applies its onError setting.

Install and mount

Maven artifact com.revokegpt:revokegpt-firewall-spring (Java 17 or later, Spring Boot 3). With revokegpt.site-key set, the auto-configuration registers RevokeGPTFilter for /* at Ordered.HIGHEST_PRECEDENCE + 10, so it sees the request before anything else can rewrite it.

Other properties: api-base, site-id, initial-fail-mode (open by default, or closed) and bundle-refresh-ms. A path segment with ; (such as /admin;jsessionid=1) counts as non-canonical.

application.properties

revokegpt.site-key=rgpk_...
revokegpt.secret-key=rgsk_...

Not published yet

This integration package is built and tested in the repository but not published to its registry yet. Install it from a checkout until the first release.

Keep routing case-sensitive

Firewall rules match paths case-sensitively, so /ADMIN is not /admin. If your origin routes case-insensitively (IIS, a case-folding proxy or framework), /ADMIN can reach the /admin handler while a rule on /admin never sees it. Make the origin case-sensitive, or write a rule for each spelling it serves.