You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Configuration option to remove Authorization header in backend calls.
No need to change any of application's user authentication method, just removing Authorization header when making backend calls.
Why is this needed?
I would like to call Azure Logic Apps as backend to this application using SAS token.
Logic Apps can include SAS token in URL for authentication.
AZURE_OPENAI_API_URL configuration should work.
But, currently backend calls also includes Authorization header, and this raises error in Logic Apps.
What would you like to be added?
Configuration option to remove Authorization header in backend calls.
No need to change any of application's user authentication method, just removing Authorization header when making backend calls.
Why is this needed?
I would like to call Azure Logic Apps as backend to this application using SAS token.
Logic Apps can include SAS token in URL for authentication.
AZURE_OPENAI_API_URL configuration should work.
But, currently backend calls also includes Authorization header, and this raises error in Logic Apps.
https://learn.microsoft.com/ja-jp/azure/logic-apps/logic-apps-securing-a-logic-app?tabs=azure-portal#generate-shared-access-signatures-sas
要求エンドポイントへの受信呼び出しでは、SAS または Azure Active Directory Open Authentication のいずれか 1 つの承認スキームのみを使用できます。 1 つのスキームを使用しても他方のスキームは無効にされませんが、両方のスキームを同時に使用すると、どちらのスキームを選択するかサービスでは不明なため、エラーが発生します。
The text was updated successfully, but these errors were encountered: