<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet href="http://bugs.horde.org/themes/feed-rss.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
 <channel>
  <title>Add User Authentication</title>
  <pubDate>Fri, 04 Jul 2008 17:29:34 -0400</pubDate>
  <link>http://bugs.horde.org/ticket/5958</link>
  <atom:link rel="self" type="application/rss+xml" title="Add User Authentication" href="http://bugs.horde.org/ticket/5958/rss" />
  <description>Add User Authentication</description>

  
  
  <item>
   <title>I request the ability to access restricted SubVersion reposi</title>
   <description>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.</description>
   <pubDate>Tue, 04 Dec 2007 11:22:47 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5958#t39352</link>
  </item>
  <item>
   <title>Done except for using Horde credentials now - I don't know a</title>
   <description>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?</description>
   <pubDate>Wed, 12 Dec 2007 16:40:02 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5958#t39746</link>
  </item>
  <item>
   <title>&gt; What you can do now is set a static username and password </title>
   <description>&gt; What you can do now is set a static username and password in 
&gt; 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.</description>
   <pubDate>Tue, 18 Dec 2007 14:00:59 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5958#t40063</link>
  </item>
  <item>
   <title>&gt; Is this in the HEAD?

Yup.</title>
   <description>&gt; Is this in the HEAD?

Yup.</description>
   <pubDate>Tue, 18 Dec 2007 14:05:08 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5958#t40066</link>
  </item>
  <item>
   <title>Finally updated from the HEAD.

Here is what the relevant </title>
   <description>Finally updated from the HEAD.

Here is what the relevant section of my sourceroots.php looks like:
$sourceroots['subversion'] = array(
        'name' =&gt; 'davisKingdom',
        'location' =&gt; 'http://XXXX.hom/svn/repos/', 
        'title' =&gt; 'Daviskingdom\'s Version Control System',
	'username' =&gt; 'xxxxx',
	'password' =&gt; 'xxxxx',
        'type' =&gt; 'svn',
);

I added the username and password options based on how I interpreted the updated Chora.php.  Perhaps I misunderstood something?</description>
   <pubDate>Wed, 19 Dec 2007 23:04:39 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5958#t40092</link>
  </item>
  <item>
   <title>Looks fine.</title>
   <description>Looks fine.</description>
   <pubDate>Thu, 20 Dec 2007 16:58:32 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5958#t40140</link>
  </item>
  

 </channel>
</rss>
