Re: [Zope] Deny public access to ZMI
Ustun Kaya wrote: > You mean running Zope behind Apache server with rewrite rule and > stuff? That's what I'm going to do unless Zope itself provides me this > functionality? It's what you should be doing anyway ;-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Deny public access to ZMI
You mean running Zope behind Apache server with rewrite rule and stuff? That's what I'm going to do unless Zope itself provides me this functionality? Best, Ustun On Tue, Jun 16, 2009 at 6:49 PM, Andreas Jung wrote: > On 16.06.09 17:36, Ustun Kaya wrote: >> Hello, >> >> Is there a straightforward way of defining which IPs are authorized to >> access to ZMI? I want to block public interface access and allow it >> only from internal network - VPN. I don't want authentication box to >> pop up to any single visitor with a browser. >> >> It is Zope 2.9.4. As I searched, I came across with docs of how to >> write scripts to define access rules to the specific folders. Should I >> go that way and implement an access rule for /manage? > I would implement such a policy within a front-end reverse proxy like > Apache. > > -aj > > ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Deny public access to ZMI
On 16.06.09 17:36, Ustun Kaya wrote: > Hello, > > Is there a straightforward way of defining which IPs are authorized to > access to ZMI? I want to block public interface access and allow it > only from internal network - VPN. I don't want authentication box to > pop up to any single visitor with a browser. > > It is Zope 2.9.4. As I searched, I came across with docs of how to > write scripts to define access rules to the specific folders. Should I > go that way and implement an access rule for /manage? I would implement such a policy within a front-end reverse proxy like Apache. -aj begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Deny public access to ZMI
Hello, Is there a straightforward way of defining which IPs are authorized to access to ZMI? I want to block public interface access and allow it only from internal network - VPN. I don't want authentication box to pop up to any single visitor with a browser. It is Zope 2.9.4. As I searched, I came across with docs of how to write scripts to define access rules to the specific folders. Should I go that way and implement an access rule for /manage? Thanks, Ustun ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
