fastapi-azure-auth: Scopes missing in /docs at each endpoint padlock
Describe the bug Scopes are missing if we select padlock symbol next to each api endpoint while trying to authorize. they do appear when we select authorize button at the top.
To Reproduce use below azure scheme
azure_scheme = SingleTenantAzureAuthorizationCodeBearer(
app_client_id=settings.APP_CLIENT_ID,
tenant_id=settings.TENANT_ID,
scopes={
f'api://{settings.APP_CLIENT_ID}/user_impersonation': 'user_impersonation',
}
)
use this scheme as a dependency to your endpoint
app.include_router(api_router, prefix=settings.API_V1_STR, dependencies=[Security(azure_scheme, scopes=['user_impersonation'])])
go to /docs

you can see scopes when you click authorize button

if you click on padlock below scopes are missing

and unable to authorize as I am getting below error…

About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 15 (13 by maintainers)
Right now both pydantic v1 and v2 works. How ever, as stated in other issues, I don’t really plan on supporting v1 pydantic other than on a backport branch for security releases.
Pydantic v1 is no longer actively developed and will only receive security fixes. I know fastapi supports both and probably will for some time, but there’s no reason for every single package out there to support both, in my opinion.
Please let me know if you disagree.
With @rhuanbarreto 's hint I can confirm the tickbox is selected automatically and it’s possible to auth in endpoints directly.
Here’s what I do for B2C:
Then use the scope in the
FastAPI.appinstance:If you preset the scope in the
swagger_ui_init_oauthoption, then you have the checkbox ticked automatically.@Pkumar-1988 , we have to wait for FastAPI maintainers (tiangolo specifically) to respond first. If they accept and merge, I’ll have to edit how we handle scopes in this package, since Azure don’t accept and respond with the same kind of scopes (unfortunately).
In other words: I have no idea, it is in FastAPIs hands now. 😊