Feature: Add support for runtime variable in auth_jwt_enabled directive #152
+40
−23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The original
auth_jwt_enabled
directive only supported static boolean values (on
/off
), which limited its flexibility for dynamic authentication control. This prevented users from implementing conditional JWT authentication based on runtime conditions such as client IP addresses, request headers, or other nginx variables.This PR enhances the
auth_jwt_enabled
directive to support nginx runtime variables, enabling dynamic control of JWT authentication based on request context. This allows for sophisticated access control scenarios such as IP-based whitelisting, conditional authentication based on request headers, or integration with nginx'smap
andgeo
modules.Use Case Example
The primary motivation is to enable VPN subnet whitelisting while maintaining JWT authentication for external traffic: