This is STILL an issue, a year and a half later. It's a huge annoyance for those of us with multiple bookmarks on the same server, combined with required periodic password changes.
There should be some way for Versions to have a "base" server bookmark, and have all other bookmarks on the same server utilize (either by default, or preference) the same login information for any other bookmarks on that same server. Can this possibly be added? In the mean time, I have to get back to changing the password on my 15+ bookmarks on my work machine. Then I get to do it on my laptop and two other machines that I use Versions on with the same server. :- ( --Steve ---------- Forwarded message ---------- From: bob <[email protected]> Date: Nov 6 2008, 1:06 pm Subject: Stored Password Issue - difficult to update To: Versions i have several bookmarks for the same repository that sits on a windows server so it uses WIndows login for auth. The company has forced password change every so few month. When this forced password happens, of course all bookmarks fails. This causes problems because that usually end up with my account being locked up due to too many failed logins. I can't even right-click bookmark to get to the password field because it seems to hit the rep with bad password anyways before bringing up the edit panel. It should not be hitting rep if it is when i right- click for edit. Alternative is to have a separate list of rep (master reps) with their own passwords then have the bookmarks reference from that. I have like 8-10 bookmarks all for the same rep and yet it is storing password separately. That drives me nuts. :) And also location of stored password seems to be confusing. Sometimes I see it show up in keychain, and other time sometimes it shows up in .subversion/auth. Exactly how does Version determine where to store or read from ? bob -- You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
