| Summary | Have to submit autologin backend twice from login.php dropdown |
| Queue | Gollem |
| Queue Version | 1.0.1 |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | slusarz (at) horde (dot) org |
| Requester | jpolansky (at) lsit (dot) ucsb (dot) edu |
| Created | 01/18/2006 (7120 days ago) |
| Due | |
| Updated | 01/20/2006 (7118 days ago) |
| Assigned | 01/19/2006 (7119 days ago) |
| Resolved | 01/20/2006 (7118 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
loginparams check should be done in Gollem::canAutoLogin() anyway).
New Attachment: gollem-h3-1.0.1-login_autologin_fix[1].patch
functionality. I have attached a new patch for redirect.php which
checks the backend config for an empty 'loginparams'. Thanks.
--Jonathan
State ⇒ Feedback
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.
Bug 3170.State ⇒ Assigned
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Have to submit autologin backend twice from login.php dropdown
Queue ⇒ Gollem
New Attachment: gollem-h3-1.0.1-login_autologin_fix.patch
State ⇒ Unconfirmed
in" button even after submitting the page by selecting a backend from
the dropdown menu (having the page submitted via the "gollem_reload"
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 "gollem_reload" javascript call), and then
the "Log in" 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'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