On Wednesday, January 18, 2012 11:24:11 AM UTC-5, Shraddha Gupta wrote: > > As 3-legged authorization requires the admin to authorize, the users wont > be able to authorize to change their passwords. > That is why, I recommended using Apps Script. You can get the new password > from your application and save it in a Google Spreadsheet in the admin's > account. If you have an Apps Script associated with spreadsheet, then you > can trigger the script every time the content of spreadsheet changes so > that script updates the password of the user. >
All right, I'll have a look at Apps Script -- that's probably what I'll go with in the end. Thanks for your advice. A few questions, though: - Are the scripts' triggers run in an asynchronous or synchronous fashion? That is, is there a way of updating the spreadsheet then waiting until the trigger has been run (and finding the results thereof -- did any errors occur during the password change attempt at the UserManager level?) so that I may tell the user whether the password change was successful or not? - How long does an onEdit trigger take to be fired? Until all the processing is done, the user's new password is in plaintext in a spreadsheet and I'm not really comfortable with that. - All in all, Apps Scipt is a fairly awkward way of doing what I want. Is there a reason why 2-legged OAuth only has read-only access to the user DB? Are there any plans to give it read/write access? -- Max -- 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/-/-ibUlnyQcXMJ. 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.
