Re: [google-appengine] Re: Prerelease SDK 1.5.5 available for download!
Well, this n00b just got caught up in _production_ documentation describing the Python 2.7 support, and wasted the last half hour trying to create and locally test such a project, wondering why the tutorial code wasn't working... It wasn't until I hit the appropriate google query matching the errors reported by the interpreter, that I found this thread and learned that the released (1.5.4) SDK does NOT support Python 2.7. Could never have discovered that from the current state of production docs. ~ The N00b -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/_EOYT3dai7AJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Prerelease SDK 1.5.5 available for download!
Yes, although after I found the forum post stating that 2.7 was not yet supported, I went back and worked through the 2.5 tutorial. I am excited about the new stuff, but was frustrated to realize that the online documentation had led me down a path I wasn't prepared to see through to the end. I'll try again tonight with the 1.5.5 SDK now that it's officially released - hadn't been able to get the prerelease SDK to work locally with 2.7 for development. Thanks for the really cool free software for us devs. Sorry I was crabby about the docs. ~Tommy K On Oct 12, 2011, at 12:28 AM, Brian Quinlan wrote: > On Tue, Oct 11, 2011 at 3:17 PM, Tommy Knowlton > wrote: >> Well, this n00b just got caught up in _production_ documentation describing >> the Python 2.7 support, and wasted the last half hour trying to create and >> locally test such a project, wondering why the tutorial code wasn't >> working... > > Hi Tommy, > > Sorry for the bad experience. Were you working through the Python 2.7 > tutorial? > > Cheers, > Brian > >> It wasn't until I hit the appropriate google query matching the errors >> reported by the interpreter, that I found this thread and learned that the >> released (1.5.4) SDK does NOT support Python 2.7. Could never have >> discovered that from the current state of production docs. >> ~ The N00b >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/google-appengine/-/_EOYT3dai7AJ. >> To post to this group, send email to google-appengine@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] HTTP Digest authentication for AppEngine?
As part of my app engine app, I'm trying to implement a WebDAV server so that users can interact with my app's blobstore using their native desktop file browser (i.e., Mac Finder.app and Windows Explorer.exe). WebDAV clients, per RFC 4918, authenticate (if at all) via HTTP Digest authentication, and I can see that I could implement this authentication method in my app only if I forego my preference for Google accounts in my app. As it is, when delegating authentication to Google accounts, Finder.app (as WebDAV client) can't correctly process the HTML authentication form that is presented on the initial request. It would be really great for my use case if some means could be added, maybe in the app.yaml handlers section, to configure HTTP Digest authentication for a chosen request path. It seems to me that the same mechanism that is currently available, that checks for a session cookie and issues the redirect to the Google account login form could instead supply the HTTP Digest nonce and challenge, along with the 401 status response to the initial unauthenticated request. I suspect there are other use cases that would benefit by an HTTP Digest authentication option, and I'm curious to know if there are other developers who want this, and what's the likelihood AppEngine will eventually incorporate such an option? Even better would be if someone could explain how I can already do this using existing support in AppEngine :) Thanks, Tommy K -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/4nzRzuJrYbIJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: HTTP Digest authentication for AppEngine?
Submitted feature request 7234<http://code.google.com/p/googleappengine/issues/detail?id=7234> . On Wednesday, March 28, 2012 12:21:52 AM UTC-6, Tommy Knowlton wrote: > > As part of my app engine app, I'm trying to implement a WebDAV server so > that users can interact with my app's blobstore using their native desktop > file browser (i.e., Mac Finder.app and Windows Explorer.exe). > > WebDAV clients, per RFC 4918, authenticate (if at all) via HTTP Digest > authentication, and I can see that I could implement this authentication > method in my app only if I forego my preference for Google accounts in my > app. As it is, when delegating authentication to Google accounts, > Finder.app (as WebDAV client) can't correctly process the HTML > authentication form that is presented on the initial request. > > It would be really great for my use case if some means could be added, > maybe in the app.yaml handlers section, to configure HTTP Digest > authentication for a chosen request path. It seems to me that the same > mechanism that is currently available, that checks for a session cookie and > issues the redirect to the Google account login form could instead supply > the HTTP Digest nonce and challenge, along with the 401 status response to > the initial unauthenticated request. > > I suspect there are other use cases that would benefit by an HTTP Digest > authentication option, and I'm curious to know if there are other > developers who want this, and what's the likelihood AppEngine will > eventually incorporate such an option? > > Even better would be if someone could explain how I can already do this > using existing support in AppEngine :) > > Thanks, > Tommy K > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/s_35RNU9-Y4J. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: HTTP Digest authentication for AppEngine?
alex, Thanks for your reply. I am using python, and webapp2, but this is the first that I've heard of a thing called @digest_auth_required. Indeed, searching the webapp2 source code supplied with the sdk, I can't find a declaration like that. Also, Google search doesn't turn up anything that points me at its documentation. Can you please send me a link to documentation, or a file and line number in webapp2 source code, where you found the decorator? Also, with regard to using a custom auth handler, it is my very strong preference, if I can figure out how to accomplish it, to allow my users to use their existing Google accounts and completely delegate identity management to Google. I am considering implementing custom authentication as a last resort at this point. (Understanding, of course, that at this point it may be the only path available to me). Thanks, Tommy K On Wed, Mar 28, 2012 at 1:45 AM, alex wrote: > What's wrong with using a custom auth handler and decorator like > @digest_auth_required? (if it's python, webapp2 is a great thing to go with) > > > On Wednesday, March 28, 2012 8:21:52 AM UTC+2, Tommy Knowlton wrote: >> >> As part of my app engine app, I'm trying to implement a WebDAV server so >> that users can interact with my app's blobstore using their native desktop >> file browser (i.e., Mac Finder.app and Windows Explorer.exe). >> >> WebDAV clients, per RFC 4918, authenticate (if at all) via HTTP Digest >> authentication, and I can see that I could implement this authentication >> method in my app only if I forego my preference for Google accounts in my >> app. As it is, when delegating authentication to Google accounts, >> Finder.app (as WebDAV client) can't correctly process the HTML >> authentication form that is presented on the initial request. >> >> It would be really great for my use case if some means could be added, >> maybe in the app.yaml handlers section, to configure HTTP Digest >> authentication for a chosen request path. It seems to me that the same >> mechanism that is currently available, that checks for a session cookie and >> issues the redirect to the Google account login form could instead supply >> the HTTP Digest nonce and challenge, along with the 401 status response to >> the initial unauthenticated request. >> >> I suspect there are other use cases that would benefit by an HTTP Digest >> authentication option, and I'm curious to know if there are other >> developers who want this, and what's the likelihood AppEngine will >> eventually incorporate such an option? >> >> Even better would be if someone could explain how I can already do this >> using existing support in AppEngine :) >> >> Thanks, >> Tommy K >> >> -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/IXVY3yUc0zYJ. > > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
