Open
Description
Describe the bug
I do have OAuth2 authentication implemented in my API.
After migrating to cadwyn versioning, the authorization through the Authorize button at the top of the swagger UI does not work anymore.
the API response I get is 404 NotFound on the /auth/login endpoint.
If I use the endpoint manually from the Swagger docs, I can sucessfully authorize against the endpoint and get back my JWT token.
I suspect, the endpoint doesn't get the proper API version header to use the correct authentication endpoint
To Reproduce
Steps to reproduce the behavior:
- Tried to login via Swagger Authorize button. I can log those header end get following API response:
DEBUG:rest_api_skeleton.app:Request headers: Headers({'host': 'localhost:1002', 'connection': 'keep-alive', 'content-length': '67', 'sec-ch-ua-platform': '"Windows"', 'authorization': 'Basic Og==', 'sec-ch-ua': '"Google Chrome";v="131", "Chromium";v="131", "Not_A Brand";v="24"', 'sec-ch-ua-mobile': '?0', 'x-requested-with': 'XMLHttpRequest', 'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36', 'accept': 'application/json, text/plain, */*', 'content-type': 'application/x-www-form-urlencoded', 'origin': 'http://localhost:1002', 'sec-fetch-site': 'same-origin', 'sec-fetch-mode': 'cors', 'sec-fetch-dest': 'empty', 'referer': 'http://localhost:1002/docs?version=2024-11-20', 'accept-encoding': 'gzip, deflate, br, zstd', 'accept-language': 'de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7', 'cookie': '_pk_id.1.1fff=2c6395af1ba573a7.1717565861.'})
INFO: 127.0.0.1:64457 - "POST /auth/login HTTP/1.1" 404 Not Found
- Manual login via endpoint from swagger UI:
DEBUG:rest_api_skeleton.app:Request headers: Headers({'host': 'localhost:1002', 'connection': 'keep-alive', 'content-length': '112', 'sec-ch-ua-platform': '"Windows"', 'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36', 'accept': 'application/json', 'x-api-version': '2024-11-20', 'content-type': 'application/x-www-form-urlencoded', 'sec-ch-ua': '"Google Chrome";v="131", "Chromium";v="131", "Not_A Brand";v="24"', 'sec-ch-ua-mobile': '?0', 'origin': 'http://localhost:1002', 'sec-fetch-site': 'same-origin', 'sec-fetch-mode': 'cors', 'sec-fetch-dest': 'empty', 'referer': 'http://localhost:1002/docs?version=2024-11-20', 'accept-encoding': 'gzip, deflate, br, zstd', 'accept-language': 'de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7', 'cookie': '_pk_id.1.1fff=2c6395af1ba573a7.1717565861.'})
INFO: 127.0.0.1:64458 - "POST /auth/login HTTP/1.1" 200 OK
Expected behavior
The Authroize button in the swagger UI should send the appropriate x-api-version header to use OAuth2 authentication
Activity
zmievsa commentedon Nov 25, 2024
Thanks for reporting this! Can I ask you to provide a code snippet that allows me to reproduce the bug?
swoKorbi commentedon Nov 25, 2024
Thanks for the quick answer:
Here is a minimal working example:
zmievsa commentedon Nov 25, 2024
Nice example! I'll try to handle this today!
zmievsa commentedon Nov 25, 2024
FastAPI generates an openapi.json that is used for rendering the swagger docs. However, it doesn't seem like swagger supports sending custom headers such as X-API-VERSION to authentication urls.
https://swagger.io/docs/specification/v3_0/authentication/
still digging
swoKorbi commentedon Nov 26, 2024
I was also playing around with openapi, but couldn't find anything that would allow me to add a custom header to the OAuth URL.
The problem definitely is in the definition of the OAuth Sheme
Python oauth2_scheme = fastapi.security.OAuth2PasswordBearer(tokenUrl="/login")
as no version for this tokenUrl can be passed with it, and therefore, the request generated in Swagger through the Authorize button can not find the endpoint as no verison is defined.I was able to get a dirty workaround by defining a login endpoint outside the versioned router and injecting the latest API version, but that is not really a satisfiying option.
I can successfully authorize through swagger with this example.
But if any changes are made to the login endpoint it will not be versioned.
zmievsa commentedon Nov 26, 2024
There is another workaround:
Essentially using API version header as an API key hence making us send it to the auth endpoint. It's a hack though and implementing it in Cadwyn would not be super easy.
zmievsa commentedon Nov 26, 2024
@swoKorbi your example actually looks quite nice! I suggest using a redirectresponse instead. I think, it will be even more stable and easy to use.
No worries. Just add a unit test (or a few) that make sure these endpoints are compatible and you'll be all set. I really like your approach and will probably add it to the docs as the current best solution.