Comments for Jim Hoskins

Comment on CherryPy Digest and Basic Authentication Tutorial by morecowbell

morecowbell — Tue, 02 Sep 2008 21:56:30 +0000

thanks for clearing that up. the example was somewhat contrived and predicated by laziness doing a “functional” redirect. obviously, that doesn’t work and you probably saved me a wild goose chase or two down the road thanks again.

Comment on CherryPy Digest and Basic Authentication Tutorial by Jim Hoskins

Jim Hoskins — Wed, 27 Aug 2008 23:30:22 +0000

@morecowbell:

I am not exactly sure what you are going for in your example, but maybe this helps.

If you want everything on your server to be protected, you can simply replace “/secure” with “/” in the configuration.

CherryPy triggers authentication before the target method is called, based on the request path. If you manually call the method, CherryPy won’t be able to tell, and authentication will not be triggered.

My suggestion would be to either:
1) Send a HTTP Redirect from root.index, this will cause the client to request /secure, and authentication will be triggered. Or,
2) Add or change the configuration to include authentication for “/” and authentiaction will trigger on any request.

The use case you suggested seems possible, if the authentication code could be implemented as a decorator, but that functionality does not exist as far as I know. I may hack around with it to see if it can be done.

I hope this helps, let me know if I didn’t fully answer your question.

Comment on CherryPy Digest and Basic Authentication Tutorial by morecowbell

morecowbell — Wed, 27 Aug 2008 21:42:57 +0000

excellent. thanks.
got a question: using the basic_auth module from above but changing RootServer class to (in order to force the sign in pop up with out the user having to follow a link, for example):
class RootServer:
s = SecureServer()
@cherrypy.expose
def index(self):
return self.s.index()

seems to circumvent the sign-in process. i was under the impression that the configuration for ‘/secure’ would still require
login and make sure that when the methods in that class are called, authentication is required. i seem to be missing something major here. thx

Comment on CherryPy Digest and Basic Authentication Tutorial by morecowbell

morecowbell — Fri, 22 Aug 2008 05:15:46 +0000

awesome. most helpful. thank you very much!

Comment on CherryPy Digest and Basic Authentication Tutorial by rohmad

rohmad — Fri, 15 Aug 2008 02:49:59 +0000

thanks alot!…its very useful

Comment on Cherrypy Digest Auth POST problem (and solution!) by Alex

Alex — Thu, 14 Aug 2008 17:05:10 +0000

Your blog is interesting!

Keep up the good work!

Comment on Cherrypy Digest Auth POST problem (and solution!) by Jim Hoskins

Jim Hoskins — Sun, 03 Aug 2008 04:22:22 +0000

Robert,

Awesome, I will have to check the version of cherrypy installed for the project in which I encountered this bug. I believe it is the latest stable. I had seen a bug report for this issue before, but It stated it had been fixed in a version prior to my current install.

I will look into it and update this article accordingly.

Comment on Cherrypy Digest Auth POST problem (and solution!) by Robert Brewer

Robert Brewer — Sun, 03 Aug 2008 04:16:21 +0000

I believe this issue was addressed in http://www.cherrypy.org/ticket/786 and http://www.cherrypy.org/ticket/819. Let us know if it persists.

Comment on CherryPy Digest and Basic Authentication Tutorial by Robert Brewer

Robert Brewer — Sun, 03 Aug 2008 04:08:44 +0000

Excellent! Thanks so much for this tutorial! We need more helpful people like you and articles like this one.

Comment on CherryPy Digest and Basic Authentication Tutorial by Green Data

Green Data — Sat, 26 Jul 2008 15:15:48 +0000

Cool man, this is really useful as I was going to implement some API (JSON) for my web application and was willing to authenticate such requests.
Anyway, I’ll add your blog into my Feed Reader as it seems that you are a Python/Cherrypy fan like me.