Google Federated Login (hybrid OpenID+OAuth) with wildcard realm -
i'm trying implement google's openid+oauth protocol, , doesn't work when openid.realm contains wildcard:
openid.realm: http://*.example.com openid.ns.oauth = http://specs.openid.net/extensions/oauth/1.0 openid.oauth.consumer = www.example.com openid.oauth.scope = https://www.googleapis.com/auth/userinfo.profile the openid process works expected, oauth extension silently ignored (no request_token in response; no error either).
as per documentation seemed supported:
use automated interface register domain, keeping in mind registered domain must consistent realm parameter being used openid. example, domain "www.somedomain.com" consistent realm of "http://*.somedomain.com".
it works realm of http://www.example.com (the callback receives request_token parameter), can't change realm since prevent existing users signing in again.
what doing wrong ?
the consumer must actual domain name, not wildcard. also, *.example.com specifies subdomain of example.com; example.com not consistent http://*.example.com
the goggle documentation unclear, may need register website google in order use openid+oauth wildcard domain. can see, johns able openid+oauth wildcard domain working out documented differences setup (other using ex2 instead of ouath namespace alias, shouldn't matter).
Comments
Post a Comment