Hey @Flowseal! I'm here to help you solve bugs, answer questions, and become a contributor. If you need any assistance, feel free to ask! To resolve the issue with the "response" not being a conform Authorization Server Metadata response, follow these steps: 1. **Protocol Matching**: Ensure that the protocol (http/https) in the Casdoor callback URL matches the protocol specified in the `AUTH_URL` setting in your `.env` file. Since your setup uses SSL, make sure both are set to `https://`. 2. **Environment Variables**: Double-check that the `AUTH_CASDOOR_ISSUER` is correctly set to match your Casdoor deployment. It should be `https://casdoor.flowseal.com` as per your setup. 3. **Casdoor Application Configuration**: - Verify that the redirect URL in your Casdoor application is correctly set to `https://lobe.flowseal.com/api/auth/callback/casdoor`. - Ensure that the `Client ID` and `Client Secret` are correctly set in your `.env` file as `AUTH_CASDOOR_ID` and `AUTH_CASDOOR_SECRET`. 4. **Additional Environment Variables**: Ensure all relevant environment variables are correctly configured: - `NEXT_AUTH_SECRET`: This should be a secure key for encrypting Auth.js session tokens. - `NEXT_AUTH_SSO_PROVIDERS`: Set this to `casdoor` to use Casdoor. - `NEXTAUTH_URL`: This should be set to `https://lobe.flowseal.com/api/auth` to specify the callback address for Auth.js during OAuth verification. 5. **Nginx Configuration**: Since you are using SSL, ensure that your Nginx configuration listens on port 443 for HTTPS and that SSL certificates are correctly configured. By ensuring these configurations are correct, you should be able to resolve the issue with the Authorization Server Metadata response ^{[[1]](https://github.com/lobehub/lobe-chat/issues/5080)}^{[[2]](https://github.com/lobehub/lobe-chat/blob/main/docs/self-hosting/advanced/auth/next-auth/casdoor.zh-CN.mdx)}^{[[3]](https://github.com/lobehub/lobe-chat/blob/main/docs/self-hosting/advanced/auth/next-auth/casdoor.mdx)}. *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- ^{Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/124d2106-0a6d-4417-a350-3e9dea603041?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/124d2106-0a6d-4417-a350-3e9dea603041?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/124d2106-0a6d-4417-a350-3e9dea603041?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/124d2106-0a6d-4417-a350-3e9dea603041?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/124d2106-0a6d-4417-a350-3e9dea603041?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/124d2106-0a6d-4417-a350-3e9dea603041?feedback_type=other)}

[Bug] "response" is not a conform Authorization Server Metadata response (unexpected HTTP status code) #5355

Company

Community

Support

Connect