Comments on: How to Setup OpenID with Google Apps

By: shawn

shawn — Thu, 10 Mar 2011 03:52:43 +0000

Thank you for this, Jeremiah. I’d be embarrassed to say how long I’ve been looking for straight-forward instructions on how to actually get OpenID working with Google Apps Premium. Yours is the only such set of instructions I’ve found, and it works as advertised.

Just in time for OpenID to go the way of the Dodo, but hey…

By: jonathan.salkoff

jonathan.salkoff — Wed, 13 Oct 2010 16:09:42 +0000

Thanks for this great guide. I am still getting prompted to download a file when I attempt to access the vanity URL. I’ve made the changes to .htaccess — any other ideas?

By: Jay

Jay — Fri, 26 Feb 2010 14:27:06 +0000

To answer everyone’s question about this, Google implemented a proof-of-concept implementation of a next-generation OpenID discovery protocol- ie it is not a full standard yet. Even when it becomes a standard, it is not backwards compatible with the OpenID 2.0 and earlier standards. Some site like StackOverflow.com, and livejournal.com, only work with OpenID 2.0 or earlier,and as such know nothing about this new discovery business. If you want to use your Google account with the older OpenID sites, check out http://openid-provider.appspot.com/ . Its sample code for the App Engine that implements an OpenID provider that should work with the older setups.

By: Jeremiah

Jeremiah — Thu, 28 Jan 2010 06:41:46 +0000

Indeed, I am getting that error with my Google Apps account. However, I am able to login using my masked Gmail Account. I’m guessing that this is a problem with StackOverflow.com, as it works properly on many other sites. Unfortunately, I don’t have an absolute answer :-\

By: mdonohue

mdonohue — Thu, 28 Jan 2010 04:32:38 +0000

The previous comment should have example.com for all the domain names.

By: mdonohue

mdonohue — Thu, 28 Jan 2010 04:30:05 +0000

This technique doesn’t seem to work on sites like stackoverflow.com. I keep seeing:

The OpenId Provider issued an assertion for an Identifier whose discovery information did not match. Assertion endpoint info: ClaimedIdentifier: http://example.com/openid?id=NNNNNNNNNNNNNNNNNNNNN ProviderLocalIdentifier: http://example.com/openid?id=NNNNNNNNNNNNNNNNNNNNN ProviderEndpoint: https://www.google.com/a/example.com/o8/ud?be=o8 OpenID version: 2.0 Service Type URIs: (unavailable) Discovered endpoint info: {ClaimedIdentifier: http://specs.openid.net/auth/2.0/identifier_select ProviderLocalIdentifier: http://specs.openid.net/auth/2.0/identifier_select ProviderEndpoint: https://www.google.com/a/dydynamic.com/o8/ud?be=o8 OpenID version: 2.0 Service Type URIs: http://specs.openid.net/auth/2.0/server, }

By: andreas.heissenberger

andreas.heissenberger — Mon, 21 Dec 2009 22:35:10 +0000

it does work with RPX but it does not work with the WordPress openID Login Plugin http://wordpress.org/extend/plugins/openid/

I allway get this message after successfull authentification at google:
Error: OpenIDloginfailed:NoOpenIDinformationfoundathttp://mydomain.com/openid?id=9999999999999999

any tipps to solve this?

thanks
Andreas

By: wccrawford

wccrawford — Tue, 29 Sep 2009 00:20:12 +0000

Nice info. I didn’t know #5, either… That’s nice.