The backend is not picked right with logout endpoint about fastapi-users

[frankie567]

Not sure if it's a bug. Could you provide the requests you are doing to /logout? I'm especially interested in the Authorization and Cookie headers.

[AndreMPCosta]

@frankie567

Here are the headers from the logout request:

{'accept': 'application/json',
 'accept-encoding': 'gzip, deflate, br',
 'cache-control': 'no-cache',
 'connection': 'keep-alive',
 'content-length': '0',
 'cookie': 'access_token=cTp7fEr8aimRK1-rvTr3PDtFXuNX4I-ZrjNbeD2AqU8',
 'host': 'localhost:8000',
 'postman-token': '129ed49e-0f6f-464d-be12-67ce7da6459f',
 'user-agent': 'PostmanRuntime/7.33.0'}

INFO:     127.0.0.1:56298 - "POST /api/v1/auth/jwt/dashboard/logout HTTP/1.1" 401 Unauthorized

[frankie567]

I'm wondering if it could come from a route priority collision (i.e. the auth_backend_mobile router may take precedence here). Could you try to disable the auth_backend_mobile router (only the router, the rest can stay) and try again?

# Comment this
#api_router.include_router(
#    fastapi_users.get_auth_router(auth_backend_mobile), prefix=jwt_url, tags=["auth"]
#)

api_router.include_router(
    fastapi_users.get_auth_router(auth_backend_dashboard), prefix=f"{jwt_url}/dashboard", tags=["auth"]
)

[AndreMPCosta]

That was the first thing I've done, but I just retried doing it again, and got the same results unfortunately.

The only two routes available:

{'accept': 'application/json',
 'accept-encoding': 'gzip, deflate, br',
 'cache-control': 'no-cache',
 'connection': 'keep-alive',
 'content-length': '0',
 'cookie': 'access_token=-DCzaUhIqZVdtidmrjZtoLDx8q2mcqkd1znDd2_VjqM',
 'host': 'localhost:8000',
 'postman-token': '9d1af03d-44b6-41b3-af3e-49dbbfc3f201',
 'user-agent': 'PostmanRuntime/7.33.0'}
INFO:     127.0.0.1:62858 - "POST /api/v1/auth/jwt/dashboard/logout HTTP/1.1" 401 Unauthorized

I am also extending the AuthenticationBackend class:

class DashBoardAuthenticationBackend(AuthenticationBackend):
    async def login(
            self, strategy: Strategy[models.UP, models.ID], user: models.UP
    ) -> Response:
        if not user.is_researcher and not user.is_superuser:
            raise HTTPException(status_code=status.HTTP_401_UNAUTHORIZED)
        token = await strategy.write_token(user)
        return await self.transport.get_login_response(token)

But I think it should not affect any of this behavior, login works as intended.

Even though I am not using the database_bearer strategy on any route now, the print that I have added on the Authenticator, still gives the database_bearer when I try to logout.
What I don't understand is that the login works as expected and the logout does not.

[AndreMPCosta]

@frankie567 I finally figured it out, the problem is on my end:

api_router.include_router(
    fastapi_users.get_auth_router(auth_backend_mobile), prefix=jwt_url, tags=["auth"]
)

api_router.include_router(
    fastapi_users.get_auth_router(auth_backend_dashboard), prefix=f"{jwt_url}/dashboard", tags=["auth"]
)

It should be:

api_router.include_router(
    fastapi_users.get_auth_router(auth_backend_mobile), prefix=jwt_url, tags=["auth"]
)

api_router.include_router(
    fastapi_users_dashboard.get_auth_router(auth_backend_dashboard), prefix=f"{jwt_url}/dashboard", tags=["auth"]
)

Because:

fastapi_users = FastAPIUsers[User, PydanticObjectId](get_user_manager, [auth_backend_mobile])
fastapi_users_dashboard = FastAPIUsers[User, PydanticObjectId](get_user_manager, [auth_backend_dashboard])

Sorry about the confusion. The current user dependency was being used from the auth_backend_mobile instead of the dashboard.