Content on main website accessible only from the portal?
We are moving from Serena-Collage Content Management System to Hannon-Hill and now would be a great time to better separate portal content from our main website. We are trying to aim our portal content at the campus internal audience; where as the main website would be for external audiences such as prospects and parents.
Our main website is on IIS while our portal is on Solaris. Does anyone know how we can designate folders on IIS protected and only accessible from the portal? We would rather not physically separate out the folders on to different servers, but might if there is no other way around it. We don't have the Luminis cms, so we don't need to worry about that. We do have several content managers that develop html in the portal, but would rather they use the cms and refer back to the page. But we don't want the internal pages accessible from the main website or the general public.
Anyone have any suggestions or methods that you used for your school?
Content on main website accessible only from the portal
Hi..
We're also using Cascade, and we went the route you mentioned later-portal content is published to the portal, main site content is published to the main site. Its just been easier for us to keep things broken down this way and from an architecture perspective, I haven't been a huge fan of interserver dependencies (our configuration is similar to yours as well).
If you want to keep your content where it is on your main site and still protect it with the portal, I believe you can do this by using CAS (Plymouth State has achieved great success going this route).
Here's a brief article by Zach talking about it...
http://nosheep.net/story/leveraging-cas-in-luminis/
The one thing you will have to do is if your pages are HTML today, they'll will have to be converted to a back-end language (such as php, jsp or whatever) to ensure the user is authenticated.
Hope this helps,
Brian