| Summary | Add User Authentication |
| Queue | Chora |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Resolved |
| Priority | 2. Medium |
| Owners | Chuck Hagenbuch <chuck (at) horde (dot) org> |
| Requester | daviskingdom (at) gmail (dot) com |
| Created | 12/04/2007 (165 days ago) |
| Due | |
| Updated | 02/24/2008 (83 days ago) |
| Assigned | |
| Resolved | 02/24/2008 (83 days ago) |
| Attachments | |
| Milestone | |
| Patch |
Assigned to Chuck Hagenbuch
Looks fine.Finally updated from the HEAD.
Here is what the relevant section of my sourceroots.php looks like:
$sourceroots['subversion'] = array(
'name' => 'davisKingdom',
'location' => 'http://XXXX.hom/svn/repos/',
'title' => 'Daviskingdom\'s Version Control System',
'username' => 'xxxxx',
'password' => 'xxxxx',
'type' => 'svn',
);
I added the username and password options based on how I interpreted the updated Chora.php. Perhaps I misunderstood something?
> Is this in the HEAD?
Yup.
> What you can do now is set a static username and password in
> sourceroots.php that will be used for everyone. Is that enough?
Sorry for the delay - I've been out of the country.
Is this in the HEAD? If so, let me test it before answering.
Static name/password for everyone isn't ideal but would probably work for ME in the near future.
If something in line with the profile idea wouldn't work prompting for name/password is a good alternative.
I'll test out the HEAD and get back to you.
State ⇒ Feedback
Done except for using Horde credentials now - I don't know about prompting the user, but we can add an option to use Horde credentials (though sort of at their own risk, since they're put on the command line - I'm actually against this unless someone *really* needs it). What you can do now is set a static username and password in sourceroots.php that will be used for everyone. Is that enough?Type ⇒ Enhancement
Queue ⇒ Chora
State ⇒ New
Summary ⇒ Add User Authentication
Priority ⇒ 2. Medium
I request the ability to access restricted SubVersion repositories using Chora. I would like the ability to access by current SVN site via Chora, but the site is password protected.
Faster solution would probably be to prompt for user name/password but passing Horde credentials could also be viable. Although the user name/password option is most flexible since users may be accessing multiple repositories - some of which they cannot control their user name / password.