search

bytebase / bytebase

The GitHub/GitLab for database DevSecOps. World's most advanced database DevSecOps solution for Developer, Security, DBA and Platform Engineering teams.
https://www.bytebase.com
Other
11.42k stars 736 forks source link

Unable to login to homepage after auth authentication is successful #9878

Open whyname opened 11 months ago

whyname commented 11 months ago

Provide the Bytebase version you are using

2.12.0

Describe the bug

Bytebase is deployed through k8s using the yaml from the official website. Besides using our own Postgres, we successfully created an admin user. However, signing in always loops back to the login page endlessly, and there are no error messages in the web page or logs.

Steps to reproduce

  1. Bytebase is deployed through k8s using the yaml from the official website. Besides using our own Postgres
  2. we successfully created an admin user
  3. sign in use this admin user
image

Expected behavior

Login into homepage

Provide the database type and version you are using

PostgreSQL 16.1

Provide the GitLab version you are using

No response

Additional context

No response

d-bytebase commented 11 months ago

Make sure you configure ingress to allow grpc web traffic to go through.

whyname commented 11 months ago

I am able to access the login page, create an admin user, and the authentication requests are also working fine. The only issue is that the page does not redirect. If grpc web is not enabled, I believe the above operations would not be possible.

image
d-bytebase commented 11 months ago

I see, we use restful http for login, static http for homepage resources, and grpc web for other API stuff. Would you help check if any web requests failed or if set cookie is returned for login? Also what's the URL, is it http or https? Thx!

Kanochiba1 commented 10 months ago

You can check back it's working on all websites now

Kanochiba1 commented 10 months ago

Working perfectly now

whyname commented 10 months ago
image

@d-bytebase When viewed from Chrome, everything looks normal. However, there is an error message in the container as follows.

time=2023-12-21T12:45:22.867Z level=ERROR source=server/routers.go:37 msg="echo request logger" method=GET uri=/auth status=404 error="code=404, message=Not Found"

d-bytebase commented 10 months ago

If Bytebase is deployed via k8s, please make sure ingress is setup right with https enabled and used.