At 12:10 PM 9/3/2004 +0200, Chris Withers wrote:
Etienne Labuschagne wrote:
What is the best way to "wrap" another live site in a Zope page or serve it through Zope.
Generally, stitch together using Apache and rewrite rules...
I have a web-enabled mail site that I must plug into a client's Plone site. The client wants his employees to first log into their Plone portal before being able to log into their web enabled mail site. He might also want all of this to happen behind https in the end. So an employee will have to do two logins to get to his/her mail.
That sucks ;-) I'd use something like CAS for single-sign-on...
I thought that too. Somehow the client feels it is more "secure" when the poor user must log in twice - sigh.
The second phase will incorporate the mail site into the Plone skin, by stripping the <head> section from the mail server served pages and then plugging the body into the body slot of the Plone skin.
niiice... rather you than me ;-)
Thanks, I feel much more confident now :(
I'd suggest just changing hte HTML of your mail software so it looks like Plone... much more efficient and robust.
My idea was for Zope to "pass on" the mail server served pages, somewhat like a reverse proxy. Maybe a reverse proxy is the answer, but how do I get the client to first log into the Plone portal before being able to
log into the mail page.
Have the mail server appear in a path within Plone's auth realm...
I have started writing a "proxy" object in Zope that takes the browser request, figures out which page to retrieve from the mail server with urllib, retrieve the page, and pass that back again, but it is a bit slow.
That will be an unending and tortuous path of pain and suffering for you ;-)
Ahh, then let's no go there, shall we? Thanks for the advice, will now go on my merry way to find enlightenment on "Have the mail server appear in a path within Plone's auth realm..." and other tidbits. Etienne
cheers,
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk