|
Wednesday 23 March 2005 2:08:27 pm
Greetings all; I have a tricky situation I am trying to get a handle on and see if it can be done with eZ publish. Here is what I need to do. I have two sites; let's call them www.foo.com and my.foo.com. eZ publish powers www.foo.com, while my.foo.com is powered by a separate system/code base. I want to manage a set of content in www.foo.com and restrict it to certain users. my.foo.com already has its own user database and login procedure. What I need to do is to be able to have people be able to login on my.foo.com or www.foo.com and have the login be persistent across the domains. Now, I think I have a decent high level view of how this should be done. These steps need to be taken: * Create a new section in eZ publish and associate the content to be protected with this section. * Setup the users/roles for that section to force a login to occur when it is accessed. * Create a custom login handler that will interface with the my.foo.com authentication system. This handler will set the cookies and/or session variables needed by both systems to ensure that the user is logged into both systems. What I am uncertain of is this. Will creating this custom login handler break the existing authentication system for the CMS/admin side of eZ publish? How far off base am I on the above? Any links, tips, etc. would be greatly appreciated. Thanks in advance.
|