Cool - I've grabbed that version and the sample page using the control
works fine! However, when trying to use it programmatically, I've
added:
OpenIdRelyingParty openid = new OpenIdRelyingParty();
IAuthenticationRequest req = null;
openid.DiscoveryServices.Clear();
openid.DiscoveryServices.Insert(0, GoogleAppsDiscovery);
req = openid.CreateRequest(domain);
var fetch = new FetchRequest();
fetch.Attributes.AddRequired
(WellKnownAttributes.Contact.Email);
req.AddExtension(fetch);
req.RedirectToProvider();
Upon returning, I still get that "The OpenID Provider issued an
assertion for an Identifier whose discovery information did not match"
error :( Shoul di be passing anything other than the domain to
CreateRequest()?
On Dec 9, 1:53 pm, Andrew Arnott <
andrewarn...@gmail.com> wrote:
> Hi iZ,
>
> You must host your own XRDS file to get Google Apps for Domains support at
> RPs that don't explicitly support Google Apps for Domains. No way around
> that -- in fact the self-hosted XRDS *is* the workaround. :)
>
> You can use it now if you'd like. Just go grab a nightly build from the
> master branch on TeamCity <
http://teamcity.dotnetopenauth.net>. Google Apps