Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Not able to login via "Welcome to Bugzilla" page

116 views
Skip to first unread message

Zarko Dudic

unread,
Feb 6, 2017, 3:52:54 PM2/6/17
to support-...@lists.mozilla.org
Hi, we've been experiencing problem login to Bugzilla via:

https://fqdn/bugzilla/index.cgi

simply a user cannot login with no specific error.

But all works well, a usea can login via

https://fqdn/bugzilla/enter_bug.cgi

The versions are:

# perl checksetup.pl
* This is Bugzilla 4.0.17 on perl 5.8.8
* Running on Linux 2.6.18-308.1.1.0.1.el5 #1 SMP Wed Mar 7 11:39:17 EST 2012

Any suggestions are highly appreciated, thanks in advance.


--
Thanks,
Zarko

Thorsten Schöning

unread,
Feb 7, 2017, 3:09:36 AM2/7/17
to support-...@lists.mozilla.org
Guten Tag Zarko Dudic,
am Montag, 6. Februar 2017 um 21:52 schrieben Sie:

> Hi, we've been experiencing problem login to Bugzilla via:
> https://fqdn/bugzilla/index.cgi
> simply a user cannot login with no specific error.

> But all works well, a usea can login via
> https://fqdn/bugzilla/enter_bug.cgi

Check your browser tools and web server log for any errors, especially
the browser tools describe you exactly what is happening with your
request and how the response looks like.

> The versions are:
[...]
> Any suggestions are highly appreciated, thanks in advance.

Upgrade everything, your versions of Bugzilla and Perl are outdated
and unsupported.

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning E-Mail: Thorsten....@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/

Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

Zarko Dudic

unread,
Feb 9, 2017, 11:42:43 PM2/9/17
to Thorsten Schöning, support-...@lists.mozilla.org
Thanks, this has been resolved.


I started with comparing Apache logs:

1. Unsuccessful login attempt:
[06/Feb/2017:17:39:53 -0800] "GET /bugzilla/index.cgi HTTP/1.1" 200 3483 "-" "Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0"

2. Successful login attempt:
[06/Feb/2017:17:40:00 -0800] "GET /bugzilla/enter_bug.cgi HTTP/1.1" 200 2238 "https://bugzilla.company.com/bugzilla/index.cgi
<https://bugzilla.oracle.com/bugzilla/index.cgi>" "Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0"

So unsuccessful one was missing the URL. I was also using Chrome console and saw messages during failed login:

***
The page at 'https://bugzilla.company.com/bugzilla/index.cgi
<https://bugzilla.oracle.com/bugzilla/index.cgi>' was loaded over a secure connection,
but contains a form which targets an insecure endpoint 'http://bugzilla.company.com/bugzilla/index.cgi
<http://bugzilla.oracle.com/bugzilla/index.cgi>'. T
his endpoint should be made available over a secure connection.
***

Next, I cloned this VM, placed with different name on our subnet and didn't have any problem with Bugzilla login.
The difference is that clone doesn't have implemented Apache certificate, since the external Bugzilla certificate is implemented on Load Balancer.

So the fix was pointing the urlbase to https, it's same as sslbase.


# diff /usr/local/bugzilla/data/params /usr/local/bugzilla/data/params-2-8-2017
97c97
< 'urlbase' => 'https://bugzilla.company.com/bugzilla/
<https://bugzilla.oracle.com/bugzilla/>',
---
> 'urlbase' => 'http://bugzilla.company.com/bugzilla/
<http://bugzilla.oracle.com/bugzilla/>',



0 new messages