Closed cullorblind closed 6 months ago
daft one, do u have any docs/guides how you setup google auth? then i can try replicate it and fix it for you 👍
I created a project on our google workspace https://console.cloud.google.com/apis/dashboard and added the following info: This should be pretty close.. It's been a while since I set it up. I don't remember anything special about it.
Enabled APIs & services: Nothing changed from defaults
Credentials Page: Name: Meshcentral Authorized Javascript origins: https://meshcentral.xxxx.net Authorized Redirect origins: https://meshcentral.xxxx.net, https://meshcentral.xxxx.net/auth-google, https://meshcentral.xxxx.net/auth-google-callback
OAuth consent screen User type: Internal
all fixed for you! took me a while to figure out the oauth setup with google. need to do some docs (remind me plz someone) bug was because the node devices dont seem to pass the name in the links where as the mesh groups do? so patched it to pass names over in the links, then it searches everywhere it can to get a name, including ur name haha
P.S: dont forget to donate ❤️ or look at my amazon wish list! https://www.si458.co.uk/2024/01/05/donation/
Describe the bug User Authorizations for a non-admin user are showing up as Google UIDs instead of friendly usernames.
To Reproduce Steps to reproduce the behavior:
If I give the user "Server Rights / Manage Users", they can then see the usernames.
Expected behavior A user should be able to see who has access or is connected to their devices by name without user admin priviledges.
Screenshots If applicable, add screenshots to help explain your problem.
Server Software (please complete the following information):
Client Device (please complete the following information):
Remote Device (please complete the following information):
Additional context This also shows when a user is looking to see who is connected to the device via the blue connection indicator. Shown here without and with user admin rights.
Your config.json file