[Zope3-checkins] CVS: Zope3/src/zope/app - _app.py:1.16.2.1

[Marius Gedminas]

Update of /cvs-repository/Zope3/src/zope/app
In directory cvs.zope.org:/tmp/cvs-serv14991/src/zope/app

Modified Files:
      Tag: mgedmin-events2-branch
	_app.py 
Log Message:
Replaced security managers and security contexts with interactions.  There is
at most one active interaction per thread, accessible with getInteraction().
Code that used getSecurityManager to get the authenticated principal should now
use the current interaction.  Note that the interaction contains an iterable of
principals instead of just one principal.  Code that used a security manager to
implement user logins should now use newInteraction/ endInteraction pair.  Code
that used a security manager to check whether the authenticated user has a
permission to do something should now ask the security policy directly (there's
a new global function getSecurityPolicy).

Interactions are tied with security policies: ISecurityPolicy has a method
used to create a new interaction for a given request.  This is not necessarily
the best idea, perhaps a global hook (setInteractionFactory) would be better.

Things not done yet:
 - Not all places in the code are ready to cope with more than one principal.
 - The README in zope.security and the sandbox security example need to be
   updated.
 - There was an idea of using a notification method in IInteraction that would
   let it customize the handling of local authentication during traversal.
   It could be e.g. afterLocalAuthentication(old_principal, new_principal, site)
   Currently the ZopePublication code just does
     interaction.remove(old_principal)
     interaction.add(new_principal)
   when request.user is changed during traversal.
 - The interaction API could be polished a bit (perhaps the request argument
   to newInteraction should be optional, perhaps there should be an alternative
   principals argument to newInteraction, perhaps endInteraction should not
   raise an exception when it is called outside of an active interaction).
 - It is not clearly cut when security checks should use the global interaction
   and when they should use the interaction of the security proxy.  Perhaps
   use the global one if interaction stored in the proxy is None?
 - It is not defined explicitly where the interaction argument can safely be
   None (as an argument to ProxyFactory, as an argument to security checkers,
   etc.).
 - Some places that construct security proxies pass None to ProxyFactory.
   Perhaps they should use the current interaction instead.  Or maybe not.





=== Zope3/src/zope/app/_app.py 1.16 => 1.16.2.1 ===
--- Zope3/src/zope/app/_app.py:1.16	Fri Feb 20 11:57:18 2004
+++ Zope3/src/zope/app/_app.py	Mon Mar  8 13:43:35 2004
@@ -24,6 +24,7 @@
 
 __metaclass__ = type
 
+
 _configured = 0
 def config(file, execute=True):
     "Configure site globals"
@@ -36,15 +37,16 @@
 
     # Set user to system_user, so we can do anything we want
     from zope.security.management import system_user
-    from zope.security.management import newSecurityManager
-    newSecurityManager(system_user)
+    from zope.security.management import newInteraction, getInteraction
+    newInteraction(None) # XXX perhaps use a special SystemConfigurationRequest
+    getInteraction().add(system_user)
 
     # Load server-independent site config
     context = xmlconfig.file(file, execute=execute)
 
     # Reset user
-    from zope.security.management import noSecurityManager
-    noSecurityManager()
+    from zope.security.management import endInteraction
+    endInteraction()
 
     _configured = execute