| Anonymous | Login | Signup for a new account | 2012-09-13 19:33 PDT |
| Main | Blog | My View | View Issues | Change Log | Roadmap | IRC Chat | Repositories | Scrum Board |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 189 | Source Integration | WebSVN | public | 2011-01-18 01:09 | 2011-01-18 01:09 | ||||||
| Reporter | obones | ||||||||||
| Assigned To | |||||||||||
| Priority | normal | Severity | minor | Reproducibility | have not tried | ||||||
| Status | new | Resolution | open | ||||||||
| Product Version | |||||||||||
| Target Version | Fixed in Version | ||||||||||
| Summary | 189: Calls to SVN should not cache authentication information | ||||||||||
| Description | Hello, When calling SVN with a login and password, the SourceSVN plugin does not indicate that those information should not be stored. As a result, when, on the same computer, someone later on uses the SVN command himself, the saved auth information is used instead which can be quite disturbing. In my case, for instance, SourceSVN uses a read only user, while, I want to use my RW user later on. As a workaround, I can specify --no-auth-cache in the configuration, but it would be much much easier if --no-auth-cache was systematically added to the command line. The attached patch does this. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2011-01-18 01:09 | obones | New Issue | |
| 2011-01-18 01:09 | obones | File Added: no-auth-cache.patch | |
| Copyright © 2000 - 2012 MantisBT Group
Time: 0.1141 seconds. memory usage: 8,316 KB |