401 HTTP Request Error

[spawar-apex]

Current Behavior

Using the Docker Container Approach, I have deployed Frontend and APIserver container on Google Cloud Platform Cloud Run service.

Both the services are running fine and both of them use container port as 8080.

When I login to the Dependency Track using Frontend URL and enter the credentials, I'l getting an error saying 401 HTTP Request Error.

Randomly, It showed me error 401 and took me to the dashboard page but as soon as I refreshed it, It again took me to the Login page.

Upon checking the logs, looks like the frontend service /api/v1/user/self and used JWT token to authenticate to the user.

I got stuck at this issue and not sure what's missing in the configuration.

Any help would be appreacited.

Steps to Reproduce

1. Deploy Frontend & API Server separately using Cloud Run Services.
2. API_BASE_URL env variable in configured in the frontend service.

Expected Behavior

Upon log in to the system, it should allow me to interact with all the admin console and the dashboard.

Dependency-Track Version

4.7.x

Dependency-Track Distribution

Container Image

Database Server

PostgreSQL

Database Server Version

15

Browser

Google Chrome

Checklist

• I have read and understand the contributing guidelines
• I have checked the existing issues for whether this defect was already reported

[spawar-apex]

Here is the error I'm getting:

{ insertId: "66437a42000440c618118ed0" labels: {1} logName: "projects//logs/run.googleapis.com%2Fstdout" receiveTimestamp: "2024-05-14T14:50:42.281638357Z" resource: {2} textPayload: "2024-05-14 14:50:42,276 INFO [JsonWebToken] Received token that did not pass signature verification" timestamp: "2024-05-14T14:50:42.278726Z"

[spawar-apex]

This was happening when I was trying to deploy OWASP Dependency Track on Google CLoud Run in GCP. Even though we deploy frontend & API using two separate services, they wont be directly able to connect to each other. This is DEPLOYMENT issue not the Dependency Track issue.