| Summary: | OpenID login window pops up suddenly | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Sam Davis <sam.davis> | ||||
| Component: | Mylyn | Assignee: | Steffen Pingel <steffen.pingel> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | 0.9 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Sam Davis
I have pushed a fix. Please reopen if you are still getting the prompt on background synchronizations after updating to the latest. Created attachment 210164 [details]
mylyn/context/zip
Thanks Steffen! I'll do that. Reopening as a reminder to push the change to split repository after the move is complete. Fixed in master. I am no longer getting the prompt, but instead, the sync just fails. When I manually refresh, the login window pops up and disappears on its own, and then the sync works. That's the expected behavior for background synchronizations. You will need to manually refresh to log-in again. We could consider prompting once or something along those lines. You will run into the same problem with any connector if you change your password on the repository or don't save it. Background synchronizations will fail and queries will decorated with the warning icon. But I didn't change my password. Is this going to happen every time I restart Eclipse? Yes, it just happened again. Note that I don't actually need to enter my credentials again, it just pops up the login window for an instant and closes it. Also, I'm using the scheduled presentation, so there's nothing to tell me that I the synchronization failed. Most people will probably never realize they may be missing incomings. (In reply to comment #10) > Yes, it just happened again. Note that I don't actually need to enter my > credentials again, it just pops up the login window for an instant and closes > it. The browser caches credentials in a cookie in this case. > Also, I'm using the scheduled presentation, so there's nothing to tell me > that I the synchronization failed. Most people will probably never realize they > may be missing incomings. Yes, it's not optimal. We could show some sort of message in the task list that authentication failed for some repositories to make this more obvious. Feel free to file a bug for that. |