Bug#822989: marked as done (sso.debian.org: Can't login using Alioth account)

["Debian Bug Tracking System" <owner@bugs.debian.org>]

Your message dated Wed, 27 Mar 2019 19:54:00 +0000
with message-id <1150e9d1-dfd9-c76b-b823-c470957a6423@thykier.net>
and subject line Re: HTTP 500 error after logging in to alioth SSO
has caused the Debian Bug report #822989,
regarding sso.debian.org: Can't login using Alioth account
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
822989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822989
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- Begin Message ---

• To: Debian Bug Tracking System <submit@bugs.debian.org>
• Subject: sso.debian.org: Can't login using Alioth account
• From: Ondřej Nový <novy@ondrej.org>
• Date: Fri, 29 Apr 2016 19:51:46 +0200
• Message-id: <146195230612.31226.2888757803052724047.reportbug@sid>

Package: sso.debian.org
Severity: grave
Justification: renders package unusable

Hi,

I can't login to sso.debian.org using my Alioth account "onovy-guest".

Error message:
Authentication failed
Invalid authenticating information

I can login directly to Alioth fine.

Thanks for fixing.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---

--- Begin Message ---

• To: 822989-done@bugs.debian.org
• Subject: Re: HTTP 500 error after logging in to alioth SSO
• From: Niels Thykier <niels@thykier.net>
• Date: Wed, 27 Mar 2019 19:54:00 +0000
• Message-id: <1150e9d1-dfd9-c76b-b823-c470957a6423@thykier.net>
• In-reply-to: <20180517131650.3yzrdyg77nihbl3w@sarek.noreply.org>
• References: <8244d132-ebf0-8582-7f47-c5a7c890bac1@overdrivenetworks.com> <20180517131650.3yzrdyg77nihbl3w@sarek.noreply.org> <20180517131650.3yzrdyg77nihbl3w@sarek.noreply.org>

On Thu, 17 May 2018 13:16:50 +0000 Peter Palfrader <weasel@debian.org>
wrote:
> Alioth has updated their ldap server's cert.  Things should work again,
> for now.
> 

>[...]
Looks like this should have been a "-done" / closing mail to the bug, so
I am taking the liberty of closing this bug now.

Thanks,
~Niels

--- End Message ---