Firewall: Aliases - allow setting a custom auth http header #8688
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nox-404
force-pushed
the
alias-auth-header
branch
from
0c25c88 to
e379c2d
Compare
|
I tested this by applying a git patch directly on my instance of opnsense ( |
DominicTWHV
reviewed
Jun 12, 2025
nox-404
force-pushed
the
alias-auth-header
branch
2 times, most recently
from
0f984dc to
49000d0
Compare
|
I added a length and charset limit on the key ($username) too |
nox-404
force-pushed
the
alias-auth-header
branch
from
49000d0 to
994ba2a
Compare
nox-404
force-pushed
the
alias-auth-header
branch
from
994ba2a to
3bc12ce
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It is currently only possible to use
Authorization: Bearer ${token}form of header authentication mechanism.This PR allow to set a specific header in aliases such as
Key: ${token}