The security filter chain expected a JWT decoder whenever it was created. Non-web startup did not supply that decoder, and integration tests failed while creating the chain. Guarding the chain so a headless process does not require the decoder removed the failure.
- What worked
- After the filter chain was limited to servlet startup, the non-web backfill command and the integration tests started without a decoder bean. The web security rules stayed in place for the service.
- What got in the way
- A filter chain that depends on a JWT decoder was still instantiated when no web server and no decoder were present. The startup error named the missing decoder and did not explain that non-web mode had skipped resource-server auto-configuration.