Hi, Alex These are my test account for thegpapastors.net username:test password:test0414
You can login with this details and gmail window will popup when u login to my site and it will struck with white page. Give me reply as soon as possible. Thank you... satya On Aug 21, 1:10 pm, "Anirudh (Google)" <[EMAIL PROTECTED]> wrote: > Hi Satya, > > I see that you had raised a support request as suggested by Alex and > were communicated to by Google Apps API team. > It would be really helpful if you can send over the test account > details through the support request for us to be able to help you. > > Thanks, > Anirudh > > On Aug 21, 12:46 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > > Hi, Alex > > > Is there any solution. Please give me reply as soon as possible. > > > On Aug 20, 11:53 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > > wrote: > > > > * Customer PIN: EDU217921 > > > * Support PIN: 59028 > > > > We have code actual code in SamlResponseTemplate.xml > > > ================================================================================ > > > <samlp:Response ID="<RESPONSE_ID>" IssueInstant="<ISSUE_INSTANT>" > > > Version="2.0" Destination="<DESTINATION>" InResponseTo="<REQUEST_ID>" > > > > xmlns="urn:oasis:names:tc:SAML:2.0:assertion" > > > > xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" > > > > xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";> > > > > <Signature xmlns="http://www.w3.org/2000/09/xmldsig#";> > > > > <SignedInfo> > > > > <CanonicalizationMethod Algorithm="http://www.w3.org/TR/ > > > 2001/REC-xml-c14n-20010315#WithComments" /> > > > > <SignatureMethod Algorithm="http://www.w3.org/2000/09/ > > > xmldsig#<RSADSA>-sha1" /> > > > > <Reference URI=""> > > > > <Transforms> > > > > <Transform Algorithm="http://www.w3.org/2000/09/ > > > xmldsig#enveloped-signature" /> > > > > </Transforms> > > > > <DigestMethod Algorithm="http://www.w3.org/2000/09/ > > > xmldsig#sha1" /> > > > > <DigestValue></DigestValue> > > > > </Reference> > > > > </SignedInfo> > > > > <SignatureValue></SignatureValue> > > > > <KeyInfo> > > > > <KeyValue></KeyValue> > > > > </KeyInfo> > > > > </Signature> > > > > <samlp:Status> > > > > <samlp:StatusCode > > > Value="urn:oasis:names:tc:SAML:2.0:status:Success"/ > > > > </samlp:Status> > > > > <Assertion ID="<ASSERTION_ID>" IssueInstant="<ISSUE_INSTANT>" > > > Version="2.0" > > > > xmlns="urn:oasis:names:tc:SAML:2.0:assertion"> > > > > <Issuer><ISSUER_DOMAIN></Issuer> > > > > <Subject> > > > > <NameID > > > > > > > Format="urn:oasis:names:tc:SAML:2.0:nameid-format:emailAddress"> > > > > <USERNAME_STRING> > > > > </NameID> > > > > <SubjectConfirmation > > > Method="urn:oasis:names:tc:SAML:2.0:cm:bearer"/ > > > > </Subject> > > > > <Conditions NotBefore="<NOT_BEFORE>" > > > > NotOnOrAfter="<NOT_ON_OR_AFTER>"> > > > > </Conditions> > > > > <AuthnStatement AuthnInstant="<AUTHN_INSTANT>"> > > > > <AuthnContext> > > > > <AuthnContextClassRef> > > > > > > > urn:oasis:names:tc:SAML:2.0:ac:classes:Password > > > > </AuthnContextClassRef> > > > > </AuthnContext> > > > > </AuthnStatement> > > > > </Assertion> > > > > </samlp:Response> > > > ============================================================================= > > > And We have renewed the code in SamlResponseTemplate.xml > > > ============================================================================= > > > <samlp:Response ID="<RESPONSE_ID>" IssueInstant="<ISSUE_INSTANT>" > > > Version="2.0" Destination="<DESTINATION>" InResponseTo="<REQUEST_ID>" > > > > xmlns="urn:oasis:names:tc:SAML:2.0:assertion" > > > > xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" > > > > xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";> > > > > <Signature xmlns="http://www.w3.org/2000/09/xmldsig#";> > > > > <SignedInfo> > > > > <CanonicalizationMethod Algorithm="http://www.w3.org/TR/ > > > 2001/REC-xml-c14n-20010315#WithComments" /> > > > > <SignatureMethod Algorithm="http://www.w3.org/2000/09/ > > > xmldsig#<RSADSA>-sha1" /> > > > > <Reference URI=""> > > > > <Transforms> > > > > <Transform Algorithm="http://www.w3.org/2000/09/ > > > xmldsig#enveloped-signature" /> > > > > </Transforms> > > > > <DigestMethod Algorithm="http://www.w3.org/2000/09/ > > > xmldsig#sha1" /> > > > > <DigestValue></DigestValue> > > > > </Reference> > > > > </SignedInfo> > > > > <SignatureValue></SignatureValue> > > > > <KeyInfo> > > > > <KeyValue></KeyValue> > > > > </KeyInfo> > > > > </Signature> > > > > <samlp:Status> > > > > <samlp:StatusCode > > > Value="urn:oasis:names:tc:SAML:2.0:status:Success"/ > > > > </samlp:Status> > > > > <Assertion ID="<ASSERTION_ID>" IssueInstant="<ISSUE_INSTANT>" > > > Version="2.0" > > > > xmlns="urn:oasis:names:tc:SAML:2.0:assertion"> > > > > <Issuer><ISSUER_DOMAIN></Issuer> > > > > <Subject> > > > > <NameID > > > > > > > Format="urn:oasis:names:tc:SAML:2.0:nameid-format:emailAddress"> > > > > <USERNAME_STRING> > > > > </NameID> > > > > <SubjectConfirmation > > > Method="urn:oasis:names:tc:SAML: > > > 2.0:cm:bearer"> > > > > <SubjectConfirmationData Recipient="<DESTINATION>" > > > NotOnOrAfter="<NOT_ON_OR_AFTER>" InResponseTo="<REQUEST_ID>"/> > > > > </SubjectConfirmation> > > > > </Subject> > > > > <Conditions NotBefore="<NOT_BEFORE>" > > > > NotOnOrAfter="<NOT_ON_OR_AFTER>"> > > > > <AudienceRestriction> > > > > <Audience><DESTINATION></Audience> > > > > </AudienceRestriction> > > > > </Conditions> > > > > <AuthnStatement AuthnInstant="<AUTHN_INSTANT>"> > > > > <AuthnContext> > > > > <AuthnContextClassRef> > > > > > > > urn:oasis:names:tc:SAML:2.0:ac:classes:Password > > > > </AuthnContextClassRef> > > > > </AuthnContext> > > > > </AuthnStatement> > > > > </Assertion> > > > > </samlp:Response> > > > ======================================================================== > > > On Aug 20, 10:33 am, "Alex (Google)" <[EMAIL PROTECTED]> wrote: > > > > > Hi Satya, > > > > > Can you submit a support request with a test user account we can use > > > > to troubleshoot this issue? Instructions for submitting a support > > > > request (including Customer and Support PIN) are in the control panel. > > > > > If the problem is with the code changes you made, can you revert the > > > > changes? > > > > > -alex > > > > > On Aug 19, 10:21 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > > > > wrote: > > > > > > Hi, My domain(thegpapastors.net) users are unable to login since from > > > > > 4days onwards. And we are getting struck in loading page when we are > > > > > trying to login using sso. We got a mail to update the aunthentication > > > > > code and > > > > > but we couldn't find where we have to update previously. Now we have > > > > > updated the authentication code in sso process. Still users are unable > > > > > to > > > > > login even we have updated the authntication code. please advice me as > > > > > soon as possible. > > > > > > Thank you. > > > > > Satya. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
