Dr. Dot, Thanks for the update.
Are you using AuthSubSessionToken? I believe this is the key to repeated interactions with your google cal over a long period of time without manual re-authorizing. Well, at least that's what the docs imply... :/ http://code.google.com/apis/accounts/docs/AuthSub.html#AuthSubSessionToken On Mon, Nov 24, 2008 at 1:31 PM, Dr. Dot <[EMAIL PROTECTED]> wrote: > > Oliver, here is an update. > > I had to "activate" my domain name inside my Google Accounts --> > https://www.google.com/accounts/ManageDomains - no problem. > I verified the domain. > I completed the Manage Your Domains form. > I created a X.509 Cert on my Web Server and uploaded to Google. > I then tested the AuthSub registration. > Everything went fine except when I test, Google intercedes with an > Access Request page and a "Grant Access" and "Deny Access" button. > > So this is where I get hung up at the moment. I have to try to figure > out how to let me Web App authenticate and connect to Google, do a > calendar update, then come back to my Web App seemlessly. > > I'll keep you posted. > > On Nov 24, 2:22 pm, "Dr. Dot" <[EMAIL PROTECTED]> wrote: >> Ok,... >> >> As for what came back on the Client Login request, it was simply the >> SID, LSID, and Auth tokens in plain text. Nothing more, nothing less. >> >> I will keep this thread going with my findings as I go. I am working >> on about 3 different projects and this is one of them. So I may or may >> not make progress daily. Check back every other day or so. >> >> I gotta believe there is a way to seamlessly integrate a Web App with >> Google Calendar. I certainly don't believe Google would make an API >> whereby someone always has to authenticate manually -- that would >> hinder what an API sets out to accomplish in the first place. >> >> On Nov 24, 2:02 pm, Oliver <[EMAIL PROTECTED]> wrote: >> >> > Hmm, I don't know if using a ClientLogin token will ultimately work >> > for you. >> >> > Fromhttp://code.google.com/apis/gdata/auth.html#ClientLogin: >> > "The token remains valid for a set length of time, defined by >> > whichever Google service you're working with." >> >> > Can you tell from what you saw on your screen how long the token >> > lasts? If it's only a little while you'll have to get a new one >> > periodically. AuthSub session tokens apparently never expire. >> >> > We may be getting into a "blind leading the blind" kind of situation >> > here because I haven't programmed this yet, I've just read the docs. >> > But I need to solve the same problem you do, so I'm eager to find out >> > how it works. keep me posted! >> >> > On Nov 24, 10:13 am, "Dr. Dot" <[EMAIL PROTECTED]> wrote: >> >> > > Hey thanks Oliver. >> >> > > I just created a simple little html form's doc and submitted. I got >> > > the Auth token back on screen. >> >> > > So if I understand what you are saying, I can just copy and paste that >> > > token into my app as the token going forward and I will always be able >> > > to integrate to my Google Calendar? If that's the case, it would be >> > > great if the Google Doc just spelled it out that this was a one-time >> > > action that you do in order to obtain the token that you ultimately >> > > embed into your Web App. BTW, I ended up using the Client Login method >> > > to obtain my token. I didn't realize it was that easy to do. >> >> > > Now I need to move into connecting to my specific calendar and coding >> > > the updates. >> >> > > Thanks Oliver! >> >> > > On Nov 24, 12:28 pm, Oliver <[EMAIL PROTECTED]> wrote: >> >> > > > I'm no expert and I didn't really understand Ray's reply, but I >> > > > thought you could use AuthSub with a session token. You just have to >> > > > store the session token on your server so that the web-app can use it. >> >> > > > Fromhttp://code.google.com/apis/accounts/docs/AuthSub.html#tokenmgmt >> >> > > > "...a session token lets the application make unlimited calls to the >> > > > Google service. Session tokens do not expire. When using session >> > > > tokens, your application should store the session token for each user >> > > > rather than requesting a new one each time it needs to access a Google >> > > > service." >> >> > > > So you would only have to manually log in once. Then your app keeps >> > > > the token and can reuse it indefinitely. >> >> > > > At least that's how I interpret it. I don't think signing out of >> > > > google invalidates the session tokens. >> >> > > > O > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" 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-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
