Perhaps you can adjust the system clock of the machine where SSO Java sample works. I have seen the message 'not yet valid' when the system clock isn't correct.
-- Takashi Matsuo On Mon, Dec 1, 2008 at 8:36 PM, ambarish <[EMAIL PROTECTED]> wrote: > > Hi, > > I am trying out the sample SSO Java client downloaded from: > http://code.google.com/apis/apps/libraries_and_samples.html#sso > > I changed the demodomain and demouser to <mydomain> and <user>. > However, when I run the sample, at the last stage, when the SAML > response is sent to google.com/a/<mydomain>acs, I get this error: > > <b> > This service cannot be accessed because your login credentials are not > yet valid. Please log in and try again. > </b> > > Apparently, this is because the public key loaded in google domain is > incorrect. How can we rectify this? > > In the sample, there is provided the following: > - DSAPrivateKey01.key > - DSAPublicKey01.key > > It is not mentioned how these keys are generated. I uploaded the > DSAPublicKey01.key, but that does not seem ok. > > Any pointers? > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
