-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Support NTLM authentication to proxy #1973
Comments
Have you tried the |
Hello Scott, Yes :) The good news is Signal detect it and use the proxy. The bad news is that the auth for this proxy is NTML and signal doesn't seems to know this auth so the proxy give me back an HTTP 407 which is the code when the auth is not good :( INFO 2018-01-17T09:05:58.188Z using proxy url http://proxybkp:8080
INFO 2018-01-17T09:06:00.490Z GET https://textsecure-service.whispersystems.org/v1/devices 407 Error
|
As I already have this issue with other open source tools, I have installed CNTLM (http://cntlm.sourceforge.net/) which create a proxy and manage the NTML auth toward enterprise proxy. |
Good to know that you were able to get it to work with that tool. I've moved this to a feature request, for supporting NTLM authentication to the proxy. |
Hello Any update? Thks |
any update on this? For those in need - px also works as workaround ( Windows only but still maintained - compared to cntlm) |
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. |
Bug description
Whatever I do Signal is seen as disconnected.
Steps to reproduce
Launch signal
Actual result:
Signal is disconnected so I cannot send or receive messages
Expected result:
Connection of signal to the server
Platform info
Signal version:
Signal Desktop v1.1.0
Operating System:
Windows 7 64-bit behind proxy with auth in NTLM
Linked device version:
Link to debug log
Because in enterprise we are after a proxy there is no dns resolution on our computer directly, it is done by the proxy itself.
The text was updated successfully, but these errors were encountered: