<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/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, 10 Apr 2026 16:48:29 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/5958</link> 
  <atom:link rel="self" type="application/rss+xml" title="Add User Authentication" href="https://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 16:22:47 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5958#t39352</link> 
  </item> 
   
  <item> 
   <title>Done except for using Horde credentials now - I don&#039;t know a</title> 
   <description>Done except for using Horde credentials now - I don&#039;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&#039;re put on the command line - I&#039;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 21:40:02 +0000</pubDate> 
   <link>https://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&#039;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&#039;t ideal but would probably work for ME in the near future.  



If something in line with the profile idea wouldn&#039;t work prompting for name/password is a good alternative.



I&#039;ll test out the HEAD and get back to you.</description> 
   <pubDate>Tue, 18 Dec 2007 19:00:59 +0000</pubDate> 
   <link>https://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 19:05:08 +0000</pubDate> 
   <link>https://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[&#039;subversion&#039;] = array(

        &#039;name&#039; =&gt; &#039;davisKingdom&#039;,

        &#039;location&#039; =&gt; &#039;http://XXXX.hom/svn/repos/&#039;, 

        &#039;title&#039; =&gt; &#039;Daviskingdom\&#039;s Version Control System&#039;,

	&#039;username&#039; =&gt; &#039;xxxxx&#039;,

	&#039;password&#039; =&gt; &#039;xxxxx&#039;,

        &#039;type&#039; =&gt; &#039;svn&#039;,

);



I added the username and password options based on how I interpreted the updated Chora.php.  Perhaps I misunderstood something?</description> 
   <pubDate>Thu, 20 Dec 2007 04:04:39 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5958#t40092</link> 
  </item> 
   
  <item> 
   <title>Looks fine.</title> 
   <description>Looks fine.</description> 
   <pubDate>Thu, 20 Dec 2007 21:58:32 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5958#t40140</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
