Bugzilla – Full Text Bug Listing
| Summary: | Repository keeps losing the password | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Andrew Gvozdev <angvoz.dev> | ||||
| Component: | Mylyn | Assignee: | Steffen Pingel <steffen.pingel> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | bugs.eclipse.org, robert.elves, shawn.minto | ||||
| Version: | dev | ||||||
| Target Milestone: | 3.6.2 | ||||||
| Hardware: | All | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Andrew Gvozdev
Shawn, what is the default location for the keystore on Windows? Andrew, what you could try to do is explicitly specifying the keystore location either through the command line or eclipse.ini (arguments have to be on separate lines: -keystore c:\eclipse.keystore . The default location for the keystore is in the Eclipse configuration directory. This means that if there is any reason that it is cleared or eclipse is unable to write to the directory, you can loose all of your passwords. Using the -keystore is a great way to ensure that even when upgrading Eclipse versions that you do not need to re-enter passwords. (In reply to comment #2) > The default location for the keystore is in the Eclipse configuration directory. > This means that if there is any reason that it is cleared or eclipse is unable > to write to the directory, you can loose all of your passwords. Using the > -keystore is a great way to ensure that even when upgrading Eclipse versions > that you do not need to re-enter passwords. Hmm, I am also used to start eclipse with -clean option after PermGen crash or eGit hanging on my big repo. Wonder if that could clear the directory. It does not clean my other settings. If it does clean - it does not do it every time though. Let me try -keystore even if it does not sound that great to me . For my work I create and remove workspaces often and requiring to remember another switch rubs me the wrong way. Also, I don't understand why upgrading eclipse versions should require re-entering passwords by default. Thanks for getting back. Please try the -keystore option. I'll mark this as resolved but feel free to reopen if the suggested solution does not address the described problem. The -keystore option did not appear to have any observable effect. The directory where it points is empty. Could you refer to any doc how to use it? I don't see it in eclipse docs http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html. It's a deprecated option but should still work. You have to point it to a file though and not a directory. From my standpoint the suggested solution does not resolve the issue. The reported issue is that bugzilla repository keeps losing the password after default eclipse installation. My points are: - Mainly - and this is the point of this bug - I think it should work out of the box normally without requiring any workaround. - Secondly (and I emphasize that it is not the main point) the suggested workaround is frankly inadequate. You ask to use deprecated and undocumented option. The option -keystore does not work for me neither as a file nor directory and I cannot find any hints on google either. The best my guess at that point is that I need to generate the keystore by some third party tool first, is it so? This is way too cumbersome for the task IMO. (In reply to comment #4) > Thanks for getting back. Please try the -keystore option. I'll mark this as > resolved but feel free to reopen if the suggested solution does not address the > described problem. I'd like to re-use this invitation to reopen the task hoping that this comment makes the complain more specific. Had one more occurrence of losing credentials yesterday. Yesterday I updated egit, also egit crashed on me and some other possible factors. Tried today to reproduce it with another egit update, killing eclipse etc. but the password stays firm. Will try more on next occasion. Still happening to me. I noticed that it happens when I create a new workspace. So it goes: 1. Open eclipse and check Eclipse.org repository credentials. User ID and password are in place, "Validate Settings" is OK with the credentials. 2. Start another instance of eclipse and create a new workspace with the "Select a workspace" launch dialog. 3. Check Eclipse.org credentials in the first instance of eclipse. They are gone. Mylyn Commons 3.6.0.v20110608-1400 org.eclipse.mylyn.commons.feature.group Eclipse Mylyn Thanks for the steps. I am tentatively putting this on for 3.6.2 to investigate further. I think I have found the problem. TasksUiPlug.loadTemplateRepositories() resets credentials when it creates pre-defined repositories that are configured for anonymous access (such as Eclipse.org) which explains the behavior described in comment 9: if (template.anonymous) { taskRepository.setCredentials(AuthenticationType.REPOSITORY, null, true); } I have committed a fix to the master and e_3_7_m_3_7_x branch. This fix will be available in the 3.6.2 (Indigo SR1) release and next weekly build. As a work around you can configure a keyring per workspace. I accidentally suggested the wrong command line options in comment#1. The right ones are: -keyring <keyring file> -password <password> Both have to be used together. Created attachment 202273 [details]
mylyn/context/zip
Thanks, the fix seems to be working. |