HTTP request seems not carry auth token when authorization chose API-Key Bearer

[joebnb]

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.1.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

this workflow works in 1.0.1 but 1.1.0 the only different is bump version and recreate docker containers

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot]

Hey @joebnb! 👋 I'm here to help you with any bugs, questions, or contributions you might have for the project. Let's tackle this issue together!

I found a similar unsolved discussion titled "Access unauthorized 401" that might be related to your issue ^[1].

For your specific problem, ensure that the API-Key Bearer token is correctly included in the HTTP request headers. In version 1.1.0, the token should be formatted as 'Bearer ' and included in the Authorization header. If the format is incorrect, it will result in authentication errors. Additionally, verify that the API key is valid and that the CORS configuration is correct, with CONSOLE_CORS_ALLOW_ORIGINS and WEB_API_CORS_ALLOW_ORIGINS properly set, typically to '*' ^[2].

If these configurations are correct and the issue persists, it might be beneficial to review the Docker environment variables related to authentication to ensure they are set up correctly for version 1.1.0 ^[3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[joebnb]

solved