feat: add AUTH_INTERCEPTOR_BYPASS token for per-request bypass #786
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.
Description
Adds support for bypassing the
AuthHttpInterceptoron a per-request basis using Angular'sHttpContextTokenpattern. This provides developers with dynamic, runtime control over token attachment without relying solely onURL-based configuration.
Changes
AUTH_INTERCEPTOR_BYPASS- AnHttpContextToken<boolean>for controlling interceptor behavior per-requestintercept()method that takes precedence overallowedListconfigurationEXAMPLES.mdwith usage examples and common scenariosUsage
Use Cases
allowedListallowedListconfiguration for specific requestsTesting
allowAnonymousconfigurationBreaking Changes
None. This is a completely additive feature that maintains full backward compatibility.
Checklist
Fixes #658