Sometimes cannot connect to domain that allow anonymous connections without logging in

vircadia / vircadia-native-core

Vircadia open source agent-based metaverse ecosystem.

https://vircadia.com/

Other

531 stars 175 forks source link

Sometimes cannot connect to domain that allow anonymous connections without logging in #940

Open JulianGro opened 3 years ago

JulianGro commented 3 years ago

When trying to connect a domain allowing anonymous connections it fails and asks you to log in. It works when logging in.

This is what I get when trying to connect to the Hub:

[01/02 10:56:44] [WARNING] [hifi.networking] The domain-server denied a connection request:  "Error decrypting username signature."  extraInfo: ""
[01/02 10:56:44] [WARNING] [hifi.networking] Make sure you are logged in to the metaverse.

Maybe this issue only happens when your token expires?

ctrlaltdavid commented 3 years ago

This appears to have been broke for a while: anonymous login works in 2020.2.5 but doesn't work in 2020.3.0 and later. 2020.3.0 release notes: https://docs.vircadia.dev/release-notes/2020-3-0-Demeter.html

digisomni commented 3 years ago

Are there any specific steps to reproduce this? I signed out and was still able to connect to the Hub without getting any prompts or failures.

JulianGro commented 3 years ago

It seems to be not 100% reliable. Dale also reported connecting to a domain while not being logged in yesterday. The People App did report his metaverse name though, which makes me think that he was logged in at least in the domain servers eyes.

ctrlaltdavid commented 3 years ago

Hmmm, I haven't been able to reproduce the problem with 2020.3.3, so far.

JulianGro commented 3 years ago

I just had a completely new person that has never run Vircadia before encounter the issue.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

JulianGro commented 3 years ago

This is still valid in 2021.1.2-rc1

odysseus654 commented 3 years ago

Looked a bit at this tonight and not really sure where to take this. This particular error message ("Error decrypting username signature.") can only happen when the interface is sending a username. Is there a stronger repro?

odysseus654 commented 3 years ago

Questions after thinking about this overnight:

If the interface attempts to log into the metaverse but fails to do so, will it still be sending a username when connecting to a domain?
Does logging a domain into the metaverse have any effect on whether users can log in via username?
During the most recent metaverse outage, would users have been able to connect if they logged out of the metaverse?

stale[bot] commented 2 years ago

Hello! Is this still an issue?