Hi,

When you use the .NET SSO sample, this two parameters will come from a
Google SAML Request.

You need to go to your Control Panel, Advanced tools Single Sign-On
section, set the Sign-in page URL to http://localhost/GoogleAppsSso/Prompt.aspx.
( the localhost, or your testserver URL is only for testing)

After this, you could try to go to any of the Apps Pages:

http://partnerpage.google.com/yourdomain.com
https://mail.google.com/a/yourdomain.com

The SAML Request will get to your SSO test page with the 2 parameters.

Julian.







On Feb 19, 9:44 am, kenlarkin <[EMAIL PROTECTED]> wrote:
> I have downloaded the .net sample code forSinglesignon and I'm not
> sure which web page to hit first.  I presume its the prompt.aspx, is
> there documentation for this that tells me this is the start page.
> Anyway this page ask for username and password and SAMLRequest and
> RelayState.  What are these are where to I get them.
>
> I have following the instruction in the readme.txt and have the
> private key and public key files created.  I have modified the
> web.config to point to these files on my machine, I have set the sso
> url to the SingleSignOnDebug.aspx web page.
>
> When I add any username and password to the prompt page without adding
> SAMLRequest and RelayState I get
> Line 52:             XmlDocument doc = new XmlDocument();
> Line 53:
> doc.LoadXml(result);                                <--Root element is
> missing.
> Line 54:
> Line 55:             return doc;
>
> Source File: C:\Projects\sso\cs\Google.Apps.SingleSignOn\src
> \SamlParser.cs    Line: 53
>
> Is there documentation I am missing?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Apps APIs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-apps-apis?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to