[Bug] Invalid ClientID error when logging in after docker compose deployment

[Hook82]

📦 Platform

Other, Self hosting Docker

📦 Deploymenet mode

server db(lobe-chat-database image)

📌 Version

main

💻 Operating System

Windows

🌐 Browser

Chrome

🐛 Bug Description

docker compose部署以后，登录时报无效的ClientID

用生成的账号密码登录casdoor，报密码错误

📷 Recurrence Steps

No response

🚦 Expected Behavior

No response

📝 Additional Information

No response

[lobehubbot]

👀 @Hook82

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot[bot]]

@Hook82 你好！我是Dosu，我是一个能够帮助您解决问题、回答疑问并成为贡献者的机器人。我会在等待人类维护者的过程中为您提供帮助。

I found some similar discussions and issues related to the "invalid ClientId" error and Casdoor login problems in the Lobe Chat application:

1. Similar Discussions:

   • A discussion titled "Casdoor的admin默认密码不是123？" mentions that the admin password might be regenerated after updates, which could be relevant if you're experiencing password issues ^[1].

2. Closed Issues:

   • An issue titled "[Bug] 无法使用管理员账号登录casdoor]([Bug] 无法使用管理员账号登录casdoor #5098)" suggests checking the init_data.json file for the password and notes that the admin password resets to the one specified in the environment configuration after running docker compose up ^[2].

For the "invalid ClientId" error, ensure that the ClientID is correctly configured and validated. The ClientID should be saved from the ZITADEL application settings and set as an environment variable AUTH_ZITADEL_ID during deployment. Make sure the ZITADEL application is configured with the correct issuer URL and that the "User Info inside ID Token" option is enabled in the Token Settings ^[3].

For troubleshooting Casdoor login issues, verify that all required environment variables are correctly set, and ensure network connectivity between the LobeChat server and Casdoor container. If authentication fails, consider hosting Casdoor on a server with proper network connectivity. Additionally, check the container logs for errors and ensure the Casdoor Webhook is correctly configured if applicable ^[4][5].

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}

[cy948]

使用的是一键部署吗？

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Is it using one-click deployment?

[Hook82]

使用的是一键部署吗？

是的，bash命令一键部署。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Is it using one-click deployment?

Yes, bash commands are deployed in one click.

[anyidea]

casdoor 登陆出问题好久了

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Casdoor login has been a problem for a long time

[cy948]

你部署的服务器能直接访问github吗？

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Can the server you deploy directly access github?

[KoellM]

你的数据库没有初始化成功，但是脚本清空了 init_data.json，之后启动成功会造成这种情况。
可以重新运行一下脚本，询问是否初始化数据库的时候选N，然后启动之后确认可以登录再清空 init_data.json

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Your database has not been initialized successfully, but the script has cleared init_data.json, and then it will be successful in startup.
You can rerun the script and ask whether to select N when clearing the database. After starting, confirm that you can log in and then clear init_data.json

[viakiba]

你的数据库没有初始化成功，但是脚本清空了 init_data.json，之后启动成功会造成这种情况。 可以重新运行一下脚本，询问是否初始化数据库的时候选N，然后启动之后确认可以登录再清空 init_data.json

按照你说的搞定了

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Your database has not been initialized successfully, but the script has cleared init_data.json, and it will cause this situation after successful startup. You can rerun the script and ask whether to select N when initializing the database. Then after starting, confirm that you can log in and clear init_data.json

As you said