How should we handle this? Would we have to pull the last login information from Google Apps, and then compare it to the last password change from AD? Is that possible (i did not create our SSO, but I need to know what to tell the people that did).
Thanks, -Dan On Wednesday, March 28, 2012 1:58:33 PM UTC-5, Jay Lee wrote: > > Hi danstl, > > Is your password sync code chanigng the Google password on *every > single SSO login?* If it is that is probably the issue, the password > should only be synced if it has change since last login. > > Jay > > On Wednesday, March 28, 2012 11:38:17 AM UTC-4, danstl wrote: >> >> Is there any resolution to this?! We use SAML SSO and sync password upon >> successful login in order to populate non-sso aware portions of Apps with >> the users password. BUT this process seems to break the ability to use >> chrome sync. You setup chrome sync, and it will sync, but then within an >> hour or two it will say : >> Account sign-in details are out of date. >> >> This is VERY frustrating because every other service works except this >> chrome sync. And since we have deployed chrome to our 650+ users this is >> becoming a pain in the butt. >> >> Anyone see this before. Its almost like chrome is looking to see if the >> password has changed, and if it has it immediately says the credentials are >> out of date... >> >> Thanks in advance! >> >> -Dan >> > -- You received this message because you are subscribed to the Google Groups "Google Apps Domain Information and Management APIs" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-apps-mgmt-apis/-/F-1Ud0j9UwUJ. 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-mgmt-apis?hl=en.
