From metatracker at psf.upfronthosting.co.za  Sun Dec  7 19:57:22 2014
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Sun, 07 Dec 2014 18:57:22 +0000
Subject: [Tracker-discuss] [issue559] Google is halting OpenID 2 support in
	April 2015
Message-ID: <1417978642.85.0.0454287505023.issue559@psf.upfronthosting.co.za>


New submission from Brett C.:

Google is shutting down there OpenID 2.0 endpoint in favour of OpenID Connect: https://developers.google.com/accounts/docs/OpenID#shutdown-timetable . They are already starting to force users to re-authenticate to get the notice that users need to switch the service they use. Full shutdown is in April.

----------
messages: 2921
nosy: brett.cannon
priority: urgent
status: unread
title: Google is halting OpenID 2 support in April 2015

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue559>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Dec  9 01:17:24 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 09 Dec 2014 00:17:24 +0000
Subject: [Tracker-discuss] [issue559] Google is halting OpenID 2 support in
	April 2015
In-Reply-To: <1417978642.85.0.0454287505023.issue559@psf.upfronthosting.co.za>
Message-ID: <1418084244.93.0.0528088313492.issue559@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Started looking into it.

----------
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue559>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Dec  9 09:17:06 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 09 Dec 2014 08:17:06 +0000
Subject: [Tracker-discuss] [issue559] Google is halting OpenID 2 support in
	April 2015
In-Reply-To: <1417978642.85.0.0454287505023.issue559@psf.upfronthosting.co.za>
Message-ID: <1418113026.55.0.703839756212.issue559@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

As of python-dev:51dd28d02f07, we now send openid_shutdown_ack in requests to Google; this should suppress the reauthentication.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue559>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Dec 10 21:41:36 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 10 Dec 2014 20:41:36 +0000
Subject: [Tracker-discuss] [issue559] Google is halting OpenID 2 support in
	April 2015
In-Reply-To: <1417978642.85.0.0454287505023.issue559@psf.upfronthosting.co.za>
Message-ID: <1418244096.95.0.0647748325018.issue559@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Starting to implement an OpenID Connect Consumer using the oic library, I fail in the first step. The OpenID specification says in

http://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata

that the issuer field of the metadata MUST be an "URL using the https scheme", yet

https://accounts.google.com/.well-known/openid-configuration

gives "accounts.google.com" as the issuer. oic then complains that claimed issuer ID and the requested issuer ID (https://accounts.google.com) are different.

Looks like a protocol violation from Google to me.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue559>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Dec 29 11:19:20 2014
From: metatracker at psf.upfronthosting.co.za (paolo cavalletti)
Date: Mon, 29 Dec 2014 10:19:20 +0000
Subject: [Tracker-discuss] [issue560] error setup msiexec.exe
Message-ID: <1419848360.01.0.436777277258.issue560@psf.upfronthosting.co.za>


New submission from paolo cavalletti:

erroe in attach

----------
files: report error.jpg
messages: 2925
nosy: paolocvl
priority: critical
status: unread
title: error setup msiexec.exe

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue560>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: report error.jpg
Type: image/pjpeg
Size: 19065 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20141229/f7fbfe98/attachment.bin>

From metatracker at psf.upfronthosting.co.za  Mon Dec 29 18:26:55 2014
From: metatracker at psf.upfronthosting.co.za (Berker Peksag)
Date: Mon, 29 Dec 2014 17:26:55 +0000
Subject: [Tracker-discuss] [issue560] error setup msiexec.exe
In-Reply-To: <1419848360.01.0.436777277258.issue560@psf.upfronthosting.co.za>
Message-ID: <1419874015.63.0.477492527928.issue560@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the report, but please create a new issue at https://bugs.python.org/ or better ask your question at https://mail.python.org/mailman/listinfo/python-list first. This tracker is for development of our Roundup instance.

----------
nosy: +berker.peksag
status: unread -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue560>
_______________________________________________________