Closed biancat821 closed 1 week ago
Hm, I wonder if the environment variables aren't set correctly. Can you check AZURE_CLIENT_APP_ID and AZURE_SERVER_APP_ID on your deployed App Service app and confirm they match the application registrations? Are you seeing this error on local dev server or deployed app?
Can you also please check the app in the portal that was setup and tell us what platforms are configured?
same issue here. Neither AZURE_CLIENT_APP_ID nor AZURE_SERVER_APP_ID were setup in either dev or deployed. I thought azd up should have filled those up when authorization is enabled. Right? Thanks.
First of all, thank you Pamela and Matt. As Evan, that is having my same issue, I do not have the AZURE_CLIENT_APP_ID nor AZURE_SERVER_APP_ID setup in. Moreover I also checked the app in the portal following the instructions in the link provided by Matt. I have the following configuration
Copying and pasting the link provided in the screenshot above I am returned with the following message.
However, when I enter the chat-app and I press the "Login" button, I am returned with the same error.
We finally managed to solve the issue. Actually in the area Registrations App of Azure we did not have the:
The problem was due to the fact that, when launching the command
azd up
the two applications mentioned above were not created.
This was caused by an error due to long path not enabled.
Therefore our solution was:
pwsh .\scripts\auth_init.ps1
azd up
This issue is for a:
Minimal steps to reproduce
Enable the authetication as described in https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/docs/login_and_acl.md#automatic-setup
The optional steps 3, 4 and 5 for ACL were skipped.
Any log messages given by the failure
AADSTS900144: The request body must contain the following parameter: 'client_id'.
Expected/desired behavior
The system allowed the user to login
OS and Version?
Windows 11
azd version?
azd version 1.8.1 (commit 88369c36ce2a0d60794389aad9b10de938f587e1)