Peter Herndon <[EMAIL PROTECTED]> writes: > I work as a sysadmin for a major hospital, and I want to build a > website that contains contact information for each server. That is, > the 24x7 operations team will be able to log in (so auth is required), > look up a server by name or IP, and get both full details on the > server as well as all the contact information of the administrators > who are responsible for the system. There are typically a primary, > secondary and tertiary contact for each server. In addition, there > are DBA contacts. And an administrative interface for adding, > modifying and deleting servers and contacts would be necessary, so two > separate levels of access will be required. I'm on the fence yet as > to whether basic use needs to be authenticated, or if it can be open > to all users on our intranet -- that will need a vote from the rest of > the sysadmins, I suppose.
Anyway, you can use the new features implemented by Jeff and published yesterday that allows using some nice things about groups and create separate groups for each "level" of authentication. > I'm looking at this as an opportunity to learn JavaScript for a second > version of the application -- the first version just needs to be > functional. With MochiKit you'll have JavaScript very fast :-) I never dealt with it before and now I have AJAX on my application and even some interesting things to make the layout better or showing/hiding some fields based on prior choices. > What is "identity", in TurboGears context? It sounds interesting, > from an authN/authZ perspective. It is authn/authz. :-) Take a look at http://groups.google.co.uk/group/turbogears/browse_thread/thread/8dc90943e2cce3ce/2c33d46b6ca2f28e#2c33d46b6ca2f28e for the things I've talked above. -- Jorge Godoy <[EMAIL PROTECTED]>
