Skip to content

http://localhost:3000/errors/server-error?error_code=500&error_message=failed+to+signin%3A+failed+to+get+token+from+casdoor #493

@Philo-theMoonLover

Description

@Philo-theMoonLover

Description
I have successfully deployed CSGHub on a Kubernetes cluster via helm chart.
Both services are running correctly and I can access the UI of each one independently via browser.

However, I am facing an issue with the login flow from CSGHub using Casdoor as the OAuth provider.

Steps to Reproduce

  1. Open CSGHub UI in browser
  2. Click Login
  3. Browser redirects to Casdoor login page
  4. Login successfully with a Casdoor account
  5. Casdoor redirects back to CSGHub

Actual Behavior
After Casdoor redirects back to CSGHub, the browser shows the following error page:
http://localhost:3000/errors/server-error?error_code=500&error_message=failed+to+signin%3A+failed+to+get+token+from+casdoor.....

Additional Observations
Both CSGHub and Casdoor UIs are accessible normally.
I can log into Casdoor directly (without going through CSGHub) works fine.

Question
Are there any known requirements or constraints regarding:

  • redirect_uri configuration
  • HTTPS/TLS enforcement
  • Domain consistency between CSGHub and Casdoor
  • Environment variables that must be explicitly set for OAuth callback handling?

Any guidance or examples for a working Casdoor + CSGHub OAuth setup on Kubernetes would be greatly appreciated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions