getting error 403 forbidden on ui and on the network tab "We're sorry but this app doesn't work properly without JavaScript enabled. Please enable it to continue."

### Current Behavior

getting below error in the network tab in the developer's tool

Dependency-Track
































































































We're sorry but this app doesn't work properly without JavaScript enabled. Please enable it to continue.

(function() {
if (!sessionStorage.length) {
// Ask other tabs for session storage
localStorage.setItem('getSessionStorage', Date.now());
}
;window.addEventListener('storage', function(event) {
if (event.key == 'getSessionStorage') {
// Some tab asked for the sessionStorage -> send it
localStorage.setItem('sessionStorage', JSON.stringify(sessionStorage));
localStorage.removeItem('sessionStorage');
} else if (event.key == 'sessionStorage' && !sessionStorage.length) {
// sessionStorage is empty -> fill it
var data = JSON.parse(event.newValue), value;
for (key in data) {
sessionStorage.setItem(key, data[key]);
}
} else if (event.key == 'sessionInvalidate') {
// clearing out session in the event a user clicks the logout button
sessionStorage.clear();
location.reload();
}
});
}
)();

### Steps to Reproduce

1. used below dependency track document to deploy dependency track using helm chart repo
https://docs.dependencytrack.org/getting-started/deploy-kubernetes/
2. after successfully deploying the dependency track. i implemented SSO using OIDC Connect protocol but getting above error while trying to login using OIDC connect
below are the configuration done in the API-SERVER and FRONTEND manifest file

API-SERVER:
- name: ALPINE_OIDC_ENABLED
value: "true"
- name: ALPINE_OIDC_ISSUER
value: https://accounts.google.com
- name: ALPINE_OIDC_CLIENT_ID
valueFrom:
secretKeyRef:
name: dtrack-db-credentials
key: clientID
- name: ALPINE_OIDC_USERNAME_CLAIM
value: email
- name: ALPINE_OIDC_TEAMS_CLAIM
value: groupList
- name: ALPINE_OIDC_USER_PROVISIONING
value: "true"

FRONTEND:
- name: OIDC_CLIENT_ID
valueFrom:
secretKeyRef:
name: dtrack-db-credentials
key: clientID
- name: API_BASE_URL
value: https://ci-dev-dt.cp.manh.cloud
- name: OIDC_ISSUER
value: https://accounts.google.com
- name: OIDC_LOGIN_BUTTON_TEXT
value: Manh Users
- name: OIDC_FLOW
value: implicit

### Expected Behavior

I am not supposed to get the 403 forbidden error on the UI. i am suppose to land on the dashboard page once i login to the page

### Dependency-Track Version

4.11.7

### Dependency-Track Distribution

Container Image

### Database Server

PostgreSQL

### Database Server Version

15

### Browser

Google Chrome

### Checklist

- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported

The issue names the Helm deployment guide and the API-SERVER and FRONTEND manifests; start by reproducing the OIDC login and inspecting the browser network response and service logs. Compare the listed OIDC and API_BASE_URL settings with the deployment documentation. Done means a successful OIDC login reaches the dashboard without a 403.

Written by the indexing model from the issue text.