Hi Bill, Thank you for your reply.
> Why not use the name & pw of the client's Gmail acct > that has the spreadsheet? Because they'll use their Google Account also for other purposes. Furthermore, when a password is changed, the corresponding webpage is not working anymore. > If the script is running on your servers how would anyone > get to your code? We work with multiple employees here and a version control system. My password would be stored in plain text in this system. Besides that, our clients mostly create their webhosting-accounts themselves and send us the login-credentials. This way, they can see my password in the script-files. Or another developer who gets access to the webhosting-account from our client.. Regards, Rob On Oct 2, 5:42 pm, Bill Hayes <bhaye...@gmail.com> wrote: > Rob, > Why not use the name & pw of the client's Gmail acct > that has the spreadsheet? > If the script is running on your servers how would anyone > get to your code? > > Regards, > Bill Hayes > > On Fri, Oct 2, 2009 at 7:06 AM, raps <robsmuld...@gmail.com> wrote: > > > Hi All, > > > I work at a web development company and we are using Google Apps. We > > start using some of the Google Apps features in cooperation with our > > clients. For example: we created a Google Spreadsheet in Google Apps, > > which our client frequently updates. The content of this spreadsheet > > is published on a part of the client's website. For this to happen, we > > created a script using the Google API's. So far, so good.. > > > However, for this to work, I hard-coded my login credentials in our > > script. My Google Account is too valuable for me to hard-code in a > > script-file. E.g. our client can gain access to this by downloading > > the appropriate file using FTP. I tried to tackle this in two ways, > > both without succes...: > > > 1. Setup a different Google Account for this particular case. > > I added a content.clientn...@mydomain.com as an E-mail alias. > > Subsequently I created a Google Account (https://www.google.com/ > > accounts/NewAccount <https://www.google.com/%0Aaccounts/NewAccount>) for > > this alias. Now I want to share the Google > > Spreadsheet with this new account. This is not working. > > I don't want to create lots of Google Apps accounts just for this > > purpose. We'll have lots of useless extra mailboxes and extra costs. > > > 2. See if i can use an encoded version of my password > > It seems the ClientLogin API doesn't work with any kind of encrypted > > password. > > > The contents need to be published on a website for all visitors, so > > letting the users login each time is not an option. > > Does anyone know how to manage Google Accounts while using them on > > lots of occassions for Google API's? > > > Thank you in advance. > > > Regards, Rob > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Docs Data APIs" group. To post to this group, send email to Google-Docs-Data-APIs@googlegroups.com To unsubscribe from this group, send email to google-docs-data-apis+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Docs-Data-APIs?hl=en -~----------~----~----~----~------~----~------~--~---
