Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#10418 closed bug (fixed)

Cannot log into bug tracker with Webpositive R1/a4 version

Reported by: vidrep Owned by: nielx
Priority: normal Milestone: R1
Component: Website/Trac Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

Try to log into bug tracker. Click log in. Indicates it is loading page, but log in fields never appear.

Attachments (1)

screenshot1.png (146.1 KB ) - added by vidrep 11 years ago.

Download all attachments as: .zip

Change History (20)

comment:1 by pulkomandy, 11 years ago

Resolution: fixed
Status: newclosed

I'm logged in right now from latest nightly. So this is already fixed.

comment:2 by korli, 11 years ago

Component: - GeneralWebsite/Trac
Resolution: fixed
Status: closedreopened

The bug seems not related to Webpositive, as it occurs on Chrome too.

comment:3 by bonefish, 11 years ago

Not sure, if it is related, ever since having updated my Linux distribution, including FireFox, about ten days ago, I also have some trouble logging in with FireFox (26.0). I figured it was an issue with the new FireFox (or some used library), since the previous version worked fine. But maybe not...

I have to remove the dev.haiku-os.org cookies to be able to log in again.

Last edited 11 years ago by bonefish (previous) (diff)

comment:4 by pulkomandy, 11 years ago

It seems Trac recently switched to a standard http-authentication dialog to an html page for login. This sounds more likely to be related, and a server-side change.

comment:5 by bonefish, 11 years ago

Owner: changed from nobody to nielx
Status: reopenedassigned

That's entirely possible. However, for me it worked fine with the FireFox version I used before. And Konqueror doesn't seem to have any trouble either.

comment:6 by umccullough, 11 years ago

In most cases, you're already logged in and just need to change the URL to use https:// instead to get it to work.

comment:7 by bonefish, 11 years ago

Oh, excellent point. The URLs in the ticket emails need to be changed accordingly.

comment:8 by nielx, 11 years ago

I changed the base_url parameter of Trac. Let's see if it contains the https now.

comment:9 by bonefish, 11 years ago

It does for the ticket URL, but not for the Trac URL:

Ticket URL: <https://dev.haiku-os.org/ticket/10418#comment:8>
Haiku <http://dev.haiku-os.org>

comment:10 by nielx, 11 years ago

Should be fixed now too.

comment:11 by vidrep, 11 years ago

Now, when I go to the bugtracker I am automatically logged in, and cannot log out. I get the error message shown it the screenshot attachment.

by vidrep, 11 years ago

Attachment: screenshot1.png added

comment:12 by vidrep, 11 years ago

After deleting cookies, and relaunching Webpositive, I was presented the normal login fields, and was able to log in normally. However, the inability to log out remains.

comment:13 by vidrep, 11 years ago

The logout problem is also occurring with hrev46706. Bug tracker started having issues with spambots around the same time. Is this related somehow?

comment:14 by vidrep, 11 years ago

I also tried logging into bug tracker using Internet Explorer 11. I was able to log in, but cannot log out.

comment:15 by vidrep, 11 years ago

Tried with Safari on my iPad - same issue.

comment:16 by umccullough, 11 years ago

The logout problem is being tracked in ticket #10656. Is the login issue mentioned here resolved now?

in reply to:  13 comment:17 by umccullough, 11 years ago

Replying to vidrep:

The logout problem is also occurring with hrev46706. Bug tracker started having issues with spambots around the same time. Is this related somehow?

Haiku revisions have pretty much nothing to do with our website or bug tracker. The login/logout and spam issues became prevalent when we moved from http digest authentication back to the default form authentication mechanism in Trac. This was done because password reset features were completely broken in the digest authentication.

comment:18 by vidrep, 11 years ago

The log in issue was resolved weeks ago. You can close this ticket.

Last edited 11 years ago by vidrep (previous) (diff)

comment:19 by umccullough, 11 years ago

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.