Username not always displayed in top left menu

[cbaker6]

New Issue Checklist

• [x] I am not disclosing a vulnerability.
• [x] I am not just asking a question.
• [x] I have searched through existing issues.
• [x] I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.

Issue Description

There's a extra text in the top left menu. See below:

Steps to reproduce

Use dashboard 4.0.0-Alpha.5

Actual Outcome

Extra text in menu

Expected Outcome

Older versions looked like:

Environment

Dashboard

• Parse Dashboard version: 4.0.0-Alpha.5
• Browser (Safari, Chrome, Firefox, Edge, etc.): Safari
• Browser version: 15.1

Server

• Parse Server version: 5.0.0-beta.4
• Operating system: Linux
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Local docker

Database

• System (MongoDB or Postgres): Postgres
• Database version: 14.1
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): Local

Logs

[parse-github-assistant[bot]]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mtrezza]

That's the username I guess.

[cbaker6]

That's the username I guess.

I believe you are right as "parse" is the default account I have setup for testing on a docker localhost.

If it is the username, it doesn't seem to show up on my deployed servers that use multiple dashboards that share the same PARSE_DASHBOARD_COOKIE_SESSION_SECRET.

Below is the screenshot of the updated:

Both use a similar configuration:

dashboard:
        image: parseplatform/parse-dashboard:4.0.0-alpha.5
        environment:
            PARSE_DASHBOARD_TRUST_PROXY: 1
            PARSE_DASHBOARD_COOKIE_SESSION_SECRET: AB8849B6-D725-4A75-AA73-AB7103F0363F # This should be constant across all deployments on your system
            MOUNT_PATH: /dashboard

The only difference is the one showing the username is a single instance on my local machine while the other are 3 instances connected behind a reverse proxy. The one behind a proxy also has 7 parse apps, while the single instance only has 1 app (goes straight to the app after login). It's also configure for multiple users while the single instance is configured for one.

Maybe one of the configurations is causing the username not to show? Maybe the username only works with one user or one app?

[mtrezza]

Maybe just a layout issue and the text is there but cut off?

[cbaker6]

Possible

[mtrezza]

Right click in the browser and look at the html code if you want to know for sure.

[cbaker6]

Seems to be a bug. When I don't see "parse" or a username, below is the browser code:

When I do see "parse" or the username:

Is there a flag somewhere that enables/disables this?

[mtrezza]

Good question, maybe it has been removed with some PR, or it has some built-in logic that hides the username on some conditions.

[cbaker6]

I can confirm the extra "parse" was indeed the username (I changed the username to see if dashboard display changed).

[mtrezza]

The dashboard user's password used to be displayed in the dashboard? It sounds quite unbelievable that such a functionality would make it into dashboard.

[cbaker6]

I meant username…

[mtrezza]

So issue can be closed?

[cbaker6]

No, the username doesn’t show up in the configuration I mentioned, so there seems to be a bug

[mtrezza]

Could you pin down in which config exactly this occurs? In your comment above you mention several factors (cookie, single instance, multiple apps) but it's not clear which one of them, or all, or which combination of these cause the issue.