<?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>Have to submit autologin backend twice from login.php dropdown</title> 
  <pubDate>Thu, 09 Apr 2026 22:17:58 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/3299</link> 
  <atom:link rel="self" type="application/rss+xml" title="Have to submit autologin backend twice from login.php dropdown" href="https://bugs.horde.org/ticket/3299/rss" /> 
  <description>Have to submit autologin backend twice from login.php dropdown</description> 
 
   
   
  <item> 
   <title>We are having issues with Gollem requiring the user to click</title> 
   <description>We are having issues with Gollem requiring the user to click the &quot;Log in&quot; button even after submitting the page by selecting a backend from the dropdown menu (having the page submitted via the &quot;gollem_reload&quot; javascript function).  Our environment consists of 3 hordeauthed/autologin backends all using FTP.



In previous versions of Gollem (~05/2004) the selected backend was loaded immediately after being selected from the dropdown on login.php.  Now it seems that the backend must be selected, the page must be reloaded (via the &quot;gollem_reload&quot; javascript call), and then the &quot;Log in&quot; button must be clicked.  I realize this might just be the way Gollem behaves now, but my org prefers the previous behavior.  I was able to make backends which are configured as hordeauthed/autologin login upon selection from the dropdown by setting $autologin to the actual value of the selected backend in the beginning of redirect.php.  I have attached a patch with the modified variable assignment.



I&#039;d appreciate any comments about a better way to deal with this issue.  Also, if this is the intended behavior, a quick note about that would be great as well.  Thanks.



--Jonathan</description> 
   <pubDate>Wed, 18 Jan 2006 22:21:26 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3299#t15686</link> 
  </item> 
   
  <item> 
   <title>See also Bug 3170.</title> 
   <description>See also Bug 3170.</description> 
   <pubDate>Thu, 19 Jan 2006 02:37:57 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3299#t15702</link> 
  </item> 
   
  <item> 
   <title>How about a compromise?  Only allow autologins in this situa</title> 
   <description>How about a compromise?  Only allow autologins in this situation *if* there are no login parameters on the login page (i.e. the ability to switch shares for SMB, the ability to set a hostname on FTP servers).  If we would allow autologins in the latter case, then we would never be able to change those parameters.</description> 
   <pubDate>Thu, 19 Jan 2006 02:44:55 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3299#t15704</link> 
  </item> 
   
  <item> 
   <title>I agree 100%.  I believe what you have described is the corr</title> 
   <description>I agree 100%.  I believe what you have described is the correct functionality.  I have attached a new patch for redirect.php which checks the backend config for an empty &#039;loginparams&#039;.  Thanks.



--Jonathan</description> 
   <pubDate>Thu, 19 Jan 2006 18:28:06 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3299#t15733</link> 
  </item> 
   
  <item> 
   <title>Actually, I&#039;ve already committed these changes yesterday (an</title> 
   <description>Actually, I&#039;ve already committed these changes yesterday (and the loginparams check should be done in Gollem::canAutoLogin() anyway).</description> 
   <pubDate>Fri, 20 Jan 2006 04:58:36 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3299#t15751</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
