-
Notifications
You must be signed in to change notification settings - Fork 602
-
Notifications
You must be signed in to change notification settings - Fork 602
All urls are not mapped by swagger #562
Comments
I think I found something relevant here, swagger only mapping those APIs which are accessible via anonymous user. As I have used permissions to block unauthorized access so swagger is bloacking all those APIs which need an auth user. So is there any setting which needs to be disable because I can pass token in API header to authenticate user. |
@verisadmin By passing in the However, if you authenticate, you should see the routes you have access to as that user. For more details: |
@marcgibbons Thx a lot. It works . One more thing I am using token Authentication. And I have custom token key for that (not usual token in DRF). I use following code in headers.
So basically I need to update headers somehow . Below are my swagger settings but still I din't have any way to add custom headers while hitting api endpoint.
|
After reading docs I found that we can define token from authorize button , But authorize button is not getting rendered for me.
I also followed #535 but no success. |
@marcgibbons It was the version issue. If version is 2.0.6 , no authorize button as soon as downgraded to 2.0.5 , authorize button appears. |
@verisadmin Yup, this regressed in 2.0.6. Fixing and will release shortly. Thanks! |
I just started using swagger for my API documentation. I followed your docs , but more then half of the urls were excluded by swagger.
Also the urls which swagger mapped to browser are not working properly, like there is no body part to test the end points. If you click Try it out! it will send the request with blank params (no body to edit request params). see image attached below
I am using APIView and I think may be this is the issue
The text was updated successfully, but these errors were encountered: