Page 1 of 1
connection rejected: user name not authorized to connect
Posted: 11 Dec 2010, 16:30
by jivvz
what does it mean? why does it happen?
it showed when trying to spectate an ongoing chicken defense game, not on an autohost, i think.
(in a messagebox)
Re: connection rejected: user name not authorized to connect
Posted: 11 Dec 2010, 16:41
by SirMaverick
jivvz wrote:what does it mean? why does it happen?
it showed when trying to spectate an ongoing chicken defense game.
(in a messagebox)
Host does not support mid join.
He needs to set AllowAdditionalPlayers=1 in springconfig.cfg / .springrc
Re: connection rejected: user name not authorized to connect
Posted: 11 Dec 2010, 16:48
by jivvz
SirMaverick wrote:
Host does not support mid join.
That's what i think it should say. or "host does not allow mid join", "host does not support joining an already running game." failproof from misunderstandings imo :]
Re: connection rejected: user name not authorized to connect
Posted: 11 Dec 2010, 16:59
by SirMaverick
You also see this message if you connect with a wrong name (+ mid join disabled). "host does not allow mid join" would be a confusing in that case.
Re: connection rejected: user name not authorized to connect
Posted: 11 Dec 2010, 17:10
by jivvz
Shouldn't you be able to split these two conditions?
I guess your stated condition is caused by the lobby sending wrong user name...? I dont see how a name can be "wrong" in any other way.
Re: connection rejected: user name not authorized to connect
Posted: 11 Dec 2010, 17:32
by SirMaverick
jivvz wrote:I dont see how a name can be "wrong" in any other way.
I'm not saying that has ever happened or is likely to happen. It was just an example.
Re: connection rejected: user name not authorized to connect
Posted: 11 Dec 2010, 17:41
by BrainDamage
by default, spring rejects any username that wasn't present in script.txt
midgame joins, dynamically adds names to that list
since the host could not add names to that list, because eg. the game is overcrowded or the user is banned, the text "username not authorized" is perfectly meaningful in all cases
Re: connection rejected: user name not authorized to connect
Posted: 11 Dec 2010, 17:55
by jivvz
I know I'm repeating myself now, but I want to reinstate my position. I think it would be of great help for users if this message got diversified.
Re: connection rejected: user name not authorized to connect
Posted: 12 Dec 2010, 14:42
by hoijui
As in practice, this is by far the most common reason, what about changing the message to something like:
connection rejected: user name not authorized to connect. (The host may not support mid-game join.)
connection rejected: user name not authorized to connect. This usually means that the host does not support mid-game join.
Would you be ok with that, BrainDamage?
Re: connection rejected: user name not authorized to connect
Posted: 12 Dec 2010, 16:06
by Satirik
SirMaverick wrote:jivvz wrote:what does it mean? why does it happen?
it showed when trying to spectate an ongoing chicken defense game.
(in a messagebox)
Host does not support mid join.
He needs to set AllowAdditionalPlayers=1 in springconfig.cfg / .springrc
this should the default value and it should be added to springsettings.exe
Re: connection rejected: user name not authorized to connect
Posted: 12 Dec 2010, 16:38
by Wombat
actually it appears when player try to rejoin before the game realizes he dropped (for some reason it lasts even 1 min)
Re: connection rejected: user name not authorized to connect
Posted: 12 Dec 2010, 16:54
by BrainDamage
Satirik wrote:SirMaverick wrote:jivvz wrote:what does it mean? why does it happen?
it showed when trying to spectate an ongoing chicken defense game.
(in a messagebox)
Host does not support mid join.
He needs to set AllowAdditionalPlayers=1 in springconfig.cfg / .springrc
this should the default value and it should be added to springsettings.exe
is IS default set to 1, and it should not be touched imo, I added it for other reasons (quick testing) and I forgot to remove it, if you want to block users from joining, simply don't send adduser from the lobby?
hoijui wrote:As in practice, this is by far the most common reason, what about changing the message to something like:
connection rejected: user name not authorized to connect. (The host may not support mid-game join.)
connection rejected: user name not authorized to connect. This usually means that the host does not support mid-game join.
Would you be ok with that, BrainDamage?
personally not much ( I have the feeling that people will misread the usually in "always" and start nagging the hosts/lobby devs in cases where they don't need to), but I have the feeling I'm a bit biased on it so go ahead if you want
Wombat wrote:actually it appears when player try to rejoin before the game realizes he dropped (for some reason it lasts even 1 min)
no, you do get a different message: "connection rejected: username already ingame" which is perfectly normal since reconnection timeout didn't expire yet
Re: connection rejected: user name not authorized to connect
Posted: 12 Dec 2010, 17:01
by SirMaverick
BrainDamage wrote:Satirik wrote:SirMaverick wrote:
He needs to set AllowAdditionalPlayers=1 in springconfig.cfg / .springrc
this should the default value and it should be added to springsettings.exe
is IS default set to 1, and it should not be touched imo
https://github.com/spring/spring/blob/8 ... r.cpp#L149
Code: Select all
allowAdditionalPlayers = configHandler->Get("AllowAdditionalPlayers", false);
Re: connection rejected: user name not authorized to connect
Posted: 12 Dec 2010, 17:08
by BrainDamage
ah sorry, that one, I was confused on the name, it was WhiteListAdditionalPlayers that I added and should be removed and forced to be true
I checked the code again to be sure, and now I can say that allowAdditionalPlayers should remain off, or anyone would be able to connect spoofing any nick, as well as be able DoS the server with connection attemps
Re: connection rejected: user name not authorized to connect
Posted: 12 Dec 2010, 17:10
by SirMaverick
BrainDamage wrote:I checked the code again to be sure, and now I can say that allowAdditionalPlayers should remain off, or anyone would be able to connect spoofing any nick, as well as be able DoS the server with connection attemps
+1
And not everyone from home has enough bandwidth to allow unknown number of additional players.