[BUG/Question] Got 'Token contains invalid claims' error for the `single tenant setup example `

[wxp16]

[BUG/Question] Got 'Token contains invalid claims' error for the `single tenant setup example `

[JonasKs]

Probably leeway again. #165
Please decode a token at jwt.io and post the claims here (you can delete sensitive data such as your name)

[JonasKs]

Also, please enable logging and send us the entire stack trace. See the troubleshooting guide: https://intility.github.io/fastapi-azure-auth/usage-and-faq/troubleshooting

[wxp16]

@JonasKs Sure.

Probably leeway again. #165 Please decode a token at jwt.io and post the claims here (you can delete sensitive data such as your name)

Probably leeway again. #165 Please decode a token at jwt.io and post the claims here (you can delete sensitive data such as your name)

Here is the decoded token:

[wxp16]

Also, please enable logging and send us the entire stack trace. See the troubleshooting guide: https://intility.github.io/fastapi-azure-auth/usage-and-faq/troubleshooting

In particular, I am able to login on the Swagger doc by clicking the lock icon on top right corner. See below screenshot

Then I click the Execute button on the Swagger doc page

Below is error logs on the server side

INFO 2023-10-26 09:41:39,833 fastapi_azure_auth Token contains invalid claims. Invalid audience
INFO:     127.0.0.1:40940 - "GET / HTTP/1.1" 401 Unauthorized

[JonasKs]

Invalid audience suggests you're not fetching the token for the backend app. You should verify your .env file has the correct IDs in the correct places.

[wxp16]

Invalid audience suggests you're not fetching the token for the backend app. You should verify your .env file has the correct IDs in the correct places.

Thanks. Fixed. Just my mistakes on my side. Thanks again for your hint.