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
I'm unfortunately experiencing a ux-breaking issue for my product.
My need is to allow multiple authentication types, as described here:
Some endpoints only require the ApiKeyAuth authentication method
Other endpoints require the ApiKeyAuthANDjwtAuth authentication methods
The issue I have is that when inputting both values in the Available authorization form:
Only the jwtAuth header (Authentication) is passed to the schema request that gets sent after I click Authorize, resulting in a schema with no endpoints (as the X-API-Key header is not being passed)
The behavior I'm looking for instead is for both headers to be sent to the schema if both are input in the Available authorizations form.
The weird thing is that if I try out the endpoints, I can see both headers being sent!
My openapi version is 3.0.3. My components section looks like this:
Dear Swagger team, thanks for your work!
I'm unfortunately experiencing a ux-breaking issue for my product.
My need is to allow multiple authentication types, as described here:
ApiKeyAuth
authentication methodApiKeyAuth
ANDjwtAuth
authentication methodsThe issue I have is that when inputting both values in the Available authorization form:
Only the
jwtAuth
header (Authentication
) is passed to the schema request that gets sent after I clickAuthorize
, resulting in a schema with no endpoints (as theX-API-Key
header is not being passed)The behavior I'm looking for instead is for both headers to be sent to the schema if both are input in the Available authorizations form.
The weird thing is that if I try out the endpoints, I can see both headers being sent!
My openapi version is 3.0.3. My components section looks like this:
And this is what the security section of my endpoints looks like:
Thank you for the help!
The text was updated successfully, but these errors were encountered: