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
Is your feature request related to a problem? Please describe.
Today the bearertokenauth (BTA) is limited to always reading from the Authorization header. This limits attributions and imposes coupling of the extension to a pipline.
Describe the solution you'd like
By allow multiple auth headers this enables easier attribution as well as decoupling of an extension from a pipeline.
The proposal is to have an extra (optional) "Header" parameter in the BTA config which can be overridden and defaults to "Authorization".
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component(s)
extension/bearertokenauth
Is your feature request related to a problem? Please describe.
Today the bearertokenauth (BTA) is limited to always reading from the Authorization header. This limits attributions and imposes coupling of the extension to a pipline.
Describe the solution you'd like
By allow multiple auth headers this enables easier attribution as well as decoupling of an extension from a pipeline.
The proposal is to have an extra (optional) "Header" parameter in the BTA config which can be overridden and defaults to "Authorization".
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: