Community
Participate
Working Groups
I have a server that needs NTLM authentication. From a desktop application I use SWT Browser authentication listener for it. After getting the event , the default credentials screen is displayed where I enter my credentials. However everytime it displays the message "Unauthorized". However the login works from Google Chrome browser. Since SWT does not use it , i cannot proceed with my application as I cannot even login.
*** Bug 497824 has been marked as a duplicate of this bug. ***
Does it work with IE browser?
No, it does not work with IE Browser. In IE, some forums suggest to change the http 1.1 setting in the browser settings to make it work. How is it possible from SWT browser?
(In reply to abhinav anand from comment #3) > No, it does not work with IE Browser. > In IE, some forums suggest to change the http 1.1 setting in the browser > settings to make it work. > > How is it possible from SWT browser? SWT Browser embeds IE by default on Windows. Can you make the change in the IE settings and try? If it works with IE, it should mostly work with the SWT Browser.
Even if it works for IE, every user will not change the browser setting for the application to work. Is there a way to do it through code?
To proceed with such bugs, we need an NTLM server in open to try. further information in needed as per comment 4.(In reply to Lakshmi Shanmugam from comment #4) > (In reply to abhinav anand from comment #3) > > No, it does not work with IE Browser. > > In IE, some forums suggest to change the http 1.1 setting in the browser > > settings to make it work. > > > > How is it possible from SWT browser? > > SWT Browser embeds IE by default on Windows. Can you make the change in the > IE settings and try? If it works with IE, it should mostly work with the SWT > Browser. Did you got a chance to try above suggestions to confirm the exact behavior ?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
