New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No authorization headers available in generated API server #2775
Comments
If you have an issue with the generated code, open the ticket on swagger-codegen. It's got nothing to do with the UI. |
FWIW, It is not clear if this is an issue in codegen or UI. |
Your definition looks correct. If it works as expected in the UI and not in the generated code... the issue is with the codegen |
Fair enough. Thanks for your quick responses. I am going to raise this in
codegen.
…On Thu, Mar 23, 2017 at 8:43 PM, Ron ***@***.***> wrote:
Your definition looks correct. If it works as expected in the UI and not
in the generated code... the issue is with the codegen
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2775 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABgyBkjpUcMqCu07Y7-OdUfNSVr_FGiSks5roxGogaJpZM4MnfEl>
.
|
@webron Sorry to be harping on this, but this also is related to the highly anticipated feature described in https://github.com//issues/1108
I have to second that request. This is kinda basic feature, in my opinion, but again, I harp. PS: I have raised this in codegen, with no response so far. |
I don't see how the generate server is related to #1108. |
Hello,
I have my security definitions in the preamble section of my
swagger.yaml
like so:And the protected routes have this:
Now, when I launch this using Swagger UI, I see the API showing up the Security section of the authentication for getting the Authorization token. Also, all the protected routes have the check box for the associated security token (Bearer). But, when I generate the
node-js
server stub and launch the server stub, I no longer see an authentication section of the API, nor it it as being included as a parameter in thebody
for the protected routes.Is this normal behavior? If not, what am I missing?
Any help is appreciated.
Thanks,
Sonny.
The text was updated successfully, but these errors were encountered: