You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
used the search to make sure that a similar issue hasn't already been submit
Expected Behavior
When there are multiple @Security() decorators in use in an OR configuration, it's expected that these will operate in a early-break pattern. Where once one is accepted, we break early.
Additionally, a way to filter security methods by say the Authentication header type (ie. Bearer, Basic ...etc) could prevent floods of rejection metrics as each auth type is evaluated.
Each security method is ran, resulting in rejections that are not actually rejections.
Possible Solution
Break early in OR scenarios, and don't execute additional security options
Allow a filter to be applied, or provided, to the decorator for control over when each security method is ran
The text was updated successfully, but these errors were encountered:
douglasg14b
changed the title
With multiple @Security() decorators, all secMethods run
With multiple @Security() decorators, all secMethods run
Dec 9, 2024
Sorting
I'm submitting a ...
I confirm that I
Expected Behavior
When there are multiple
@Security()
decorators in use in anOR
configuration, it's expected that these will operate in aearly-break
pattern. Where once one is accepted, we break early.Additionally, a way to filter security methods by say the Authentication header type (ie.
Bearer
,Basic
...etc) could prevent floods of rejection metrics as each auth type is evaluated.Current Behavior
Each security method is ran, resulting in rejections that are not actually rejections.
Possible Solution
OR
scenarios, and don't execute additional security optionsThe text was updated successfully, but these errors were encountered: