-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trouble authenticating user #100
Comments
Here's my index.js:
|
Fixed it! The line I'm not sure if this only affects nw.js developers or not. Maybe worth putting a note in the code about it? I dunno. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am having trouble authenticating my app's node user. Here is my setup:
client.authenticate( userName );
is called.<W>2017-10-12 09:44:06.022 1 => <70:(-1)> New connection: 127.0.0.1:49475
<W>2017-10-12 09:44:06.022 Connection: Failed to add flow to QOS
<W>2017-10-12 09:44:06.077 1 => <70:TestUserName(-1)> Authenticated
...That middle line seems to be a clue. That last line seems to indicate that the app/node user is authenticated, but I still don't see the 'authenticate' event firing in the app (via callback statements).
Any thoughts?
------------Edit--------------
Re: 5) above, I don't think that QOS message is an issue. I get that when my normal mumble client runs on my computer, and it connects and has full functionality. (When I connect over a network from another device, I don't get it, meaning that this is likely an end-to-end encryption check that will fail when the client and server are on the same machine.)
The real issue seems to be the the 'initialize' callback never firing. That is what I'm trying to ultimately gain access to so I can start customizing the functionality for my app. I seem to be authenticating fine, otherwise the server wouldn't send back the channel/user states. Just looking for that pesky callback to fire!
Thank you in advance for any help you can provide.
The text was updated successfully, but these errors were encountered: