Yes i would use that to force the user to change the password on first
login but i need some variable to figure out which one is a new
account and then change that password, i know the administration
dashboard shows whether a password has been set by an administrator or
is a temporary password, i need something like that
thanks,
fatima

On Mar 11, 8:14 am, Takashi Matsuo <[email protected]> wrote:
> Hi,
>
> Perhaps you can update user with the Attribute
> 'changePasswordAtNextLogin' of the Element 'login' set to 'true',
> using provisioning API.
>
> That force the user to change his/her password at next login.
>
> hope it helps
>
> -- Takashi Matsuo
>
>
>
> On Wed, Mar 11, 2009 at 5:21 AM, fatima <[email protected]> wrote:
>
> > We are planning to synchronize creating accounts with our Active
> > Directory using the Google Directory Sync for provisoining accounts
> > after a fixed interval. With active directory GDS does not use the
> > password field and generates a random password for each user.
> > I need to be able to change those passwords before allowing users to
> > log in and change their own passwords. I havent been able to find any
> > creation or time information on which i could make a decision about
> > changing passwords after every sync.
> > Any suggestions? I am using the Java provisioning API, only because it
> > had the group creation which python didnt. I would also like to set
> > certain Settings in the new accounts that are created using Email
> > Settings API. I have seen the XML posts for it but has anyone used it
> > in Java.
>
> > Thanks
>
> > fatima- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
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