| Summary: | [Net] username, password of manual Proxy is not persisted. | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Oleg Besedin <ob1.eclipse> |
| Component: | Team | Assignee: | Malgorzata Janczarska <malgorzata.tomczyk> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | henrich.kraemer, kazm, ob1.eclipse, pawel.pogorzelski1, slewis, Szymon.Brandys, tjwatson, wojciech.galanciak |
| Version: | 3.6 | ||
| Target Milestone: | 3.8 M4 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Oleg Besedin
I'd suggest adding an extra error dialog to the ProxyType.saveProxyAuth(). At present it catches StorageException and logs it. I would suggest to add an extra error message along the lines of "Unable to save the proxy authorization information. You can use Secure Storage preferences page to delete corrupted data (see "Contents" tab)." Depending on how sophisticated you'd like to make it, it could be just an extra text written in the error log, or a message dialog, or even a message dialog with the link to open the Secure Storage preference page. Moving to 3.7. Oleg, I was not able to reproduce this bug. Does it require any specific corruption of secure storage? From another hand there might be also several other reproduction steps when similar log error appears and there is no dialog. My example tested scenario: 1. Set proxy username/password in Eclipse 2. Close Eclipse 3. Modify following (or similar) line in your secure_storage: /org.eclipse.core.net.proxy.auth/HTTP/user=org.eclipse.equinox.security.windowspasswordprovider\tFtPtqIglboo\=,mFONfYtLvsQ\= to this one /org.eclipse.core.net.proxy.auth/HTTP/user=org.eclipse.equinox.security.windowspasswordprovider\twC 4. Start Eclipse. Another example is deleting security_storage file between Eclipse sessions. In such case you don't have even any error message in the log despite the fact proxy preferences have been changed. Szymon do we want to fix in net.ui kinds of bugs related to broken/incomplete security storage? Oleg, I was also unable to reproduce this problem. Do you know what should I do with my secure storage to reproduce it? (In reply to comment #1) > At present it catches StorageException and logs it. Can you attach this log? (In reply to comment #4) > Oleg, I was also unable to reproduce this problem. I cannot reproduce using N20111114-2115. (In reply to comment #5) > (In reply to comment #4) > > Oleg, I was also unable to reproduce this problem. > > I cannot reproduce using N20111114-2115. Marking as WORKSFORME, because probably it's to be no longer reproduceable. |