On Aug 3, 12:08 am, Holger <[email protected]> wrote: > The difficulty depends on how 'safe' the solution should be.
Fort Knox of course. ;) No, this is just something to share pics and vids with the family so it doesn't have to be guaranteed secure. Just secure enough to keep casual browsers from viewing it all. > An easy form of authorization proof would be a MD5 hash of a secret > string plus date and hour. Your user could extract the url, but this > url would work within the current hour only. Your sequence is pretty much what I had in mind. I think I got caught up in requiring the third-party server to be able to determine if the user was authenticated via their Google account. Your MD5 suggestion is super simple and would work good enough for my purposes. If it doesn't, I can always enhance it with something like your multi redirection approach. Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" 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-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
