microsoft / azurechat

🤖 💼 Azure Chat Solution Accelerator powered by Azure Open AI Service
MIT License
1.25k stars 1.22k forks source link

local clone cannot access the api of extension like BingSearch and AI Search #420

Open jnxjent opened 2 months ago

jnxjent commented 2 months ago

Hi! I have an issue that the localclone cannot access the api of AI Seach and Bing as "API is not authorized" while other function like chat is working without problem as well as the remote of the clone . I did "AdditionallyAllowedTenant=* in env.local file but nothing change . Strangely, the setting of extension is synchronized with local's, namely, when I change the setting of the remote is relected to local's immediately. I wisht to use the functionality of AI Search because I believe Search resource is necessary for upload the file or search the previous uploaded file because I wisht to check the customized function at localclone prior to push to the Remote. Appreciate if somebody advise how to solve this issue.

fsch-ppi commented 3 weeks ago

The headers are stored in AzureKeyVault and not locally.

If you inspect the header calls being made locally - you will see that the value of all headers are the "**" mask.

You would have to modify this function (in chat-api-dynamic-extension.ts): Image

Add a check before the return statement, that checks if the h.key is present in your local env file and if so return the value from your env file as "value"