[BDS-6043] whitelist add cmd adds incomplete entry to whitelist.json Created: 14/Jun/20 Updated: 29/Jan/21 Resolved: 29/Jan/21 |
|
| Status: | Resolved |
| Project: | Bedrock Dedicated Server |
| Affects Version/s: | 1.14.60 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Christopher Fromknecht | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Windows 10 Edu 2004/1909, AMD 3900 CPU, 32Gb 3600 DDR4, MCBEPlay Front End |
||
| Confirmation Status: | Unconfirmed |
| Description |
|
I can execute 'whitelist add [player tag]' and observe the whitelist.json update with the player tag only. When I turn white-list=false in the server.properties and do an whitelist add, the xuid is also added. With the white-list=true is set, only the player tag is added and the whitelist but that player will be denied access to the world (no xuid).
Background, I set up a server for a very select, controlled group of players, and need to strictly control access. The current work-around I am using is having the new player log into an unrestricted "lobby" world so I can collect the player tag and the xuid. I then use that information and manually update the whitelist.json file for the controlled world. Then shut down the lobby until a new player is invited. The other workaround would be turn off the whitelist temporarily, allow the player in, add to the whitelist, then turn whitelist back on. Either workaround works but is cumbersome.
Maybe update the whitelist.json when the new player first logs in? Additionally, the console does not output any non-whitelist player attempt to logging into the world (as far as I can tell). |
| Comments |
| Comment by [Mojang] Mega_Spud (Jay Wells) [ 29/Jan/21 ] |
|
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem. Quick Links: |
| Comment by IonicEcko [ 16/Jun/20 ] |
|
When adding someone to the whitelist via console it only adds them via Gamertag. This is expected, it does no lookup to get an XUID when you add the player. However when the player first joins the entry will be updated with their XUID. This shouldn't be any different between online mode off and on and I wasn't able to reproduce any difference. If your players are unable to enter once whitelisted its likely you're either not whitelisting them correctly, this can be due to 2 main causes.
If you still believe there to be an issue please provide steps to reproduce the issue from a brand new world and outside of the MCBEPlay utility. While its a great tool, bugs can only be accepted when they can be reliably reproduced in the vanilla server software. |
| Comment by Christopher Fromknecht [ 14/Jun/20 ] |
|
Some additional info that I just found. The gamer-tags in question were the older gamer-tags (without the 4 digit numerical suffex). Changed the gamer tag for one of my kids and noted the whitelist updated with the new tag without any manual intervention. Unsure if this issue is only with the older format tag or affects both the new and old formats. |