Google SSO not working

I am using Component space SSO for google Sign in. I get the below Error.



My saml config is

<PartnerServiceProvider Name=“google.com/a/mydomian.com”
WantAuthnRequestSigned=“false”
SignSAMLResponse=“false”
SignAssertion=“false”
EncryptAssertion=“false”
NameIDFormat=“urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress”
AssertionConsumerServiceUrl=“<a href=“https://www.google.com/a/mydomian.com/acs” “=””><a href=“https://www.google.com/a/mydomian.com/acs” “=”“><a href=“https://www.google.com/a/mydomian.com/acs””>https://www.google.com/a/mydomian.com/acs"
PartnerCertificateFile=“Mycer.cer”/>


My Code

public ActionResult SingleSignOnGoogle() {

string partnerSP = “google.com/a/mydomain.com”;
string targetUrl = “<a href=“https://mail.google.com/a/mydomain.com” ;”=“”><a href=“https://mail.google.com/a/mydomain.com” ;“=”"><a href=“https://mail.google.com/a/mydomain.com";">https://mail.google.com/a/mydomain.com”;
string userName = “user1@mydomain.com”;

IDictionary<string, string> attributes = new Dictionary<string, string>();

foreach (string key in WebConfigurationManager.AppSettings.Keys) {
if (key.StartsWith(AppSettings.Attribute)) {
attributes[key.Substring(AppSettings.Attribute.Length + 1)] = WebConfigurationManager.AppSettings[key];
}
}

SAMLIdentityProvider.InitiateSSO(
Response,
userName,
attributes,
targetUrl,
partnerSP);

return new EmptyResult();
}


My Google Settings




You need to sign the SAML response. Make sure that SignSAMLResponse is set to true in your saml.config.
Also, the verification certificate configured in Google must match with the PFX file configured for your identity provider.

[quote]
ComponentSpace - 9/25/2016
You need to sign the SAML response. Make sure that SignSAMLResponse is set to true in your saml.config.
Also, the verification certificate configured in Google must match with the PFX file configured for your identity provider.
[/quote]

Hi Setting the SignsSAMLResponse as true solved my problem. Thanks a lot

Thanks Kiran for the update. I’m glad that fixed the issue.