Re: Envolution proposal idea

On Sun, 2002-09-15 at 10:49, James Pegram wrote:
> For example. Our helpdesk system is accessed by logging into the website. Once a user has logged in they get a block that displays links to the applications they have access to. In this example, the application is launched from a different server on a different domain as the main website. However, by passing the session id to this code snippet I can effectively *pass* the entire session to another application. The applciations internal user management then takes over. However the main sites iis still in effect. If you logout of the main website, your logged out of everything you have open at the time.
> So, like you, I have a need for which the CMS concept sorta fits. Primarily there are pieces of it that solve exiting problems I have. My chief complaint is most everyone uses the CMS as a personal website tool to display news. Nothing else. Most everything I come up with is becuase I have it in a real world environment where the core website means very little. Sounds like your wanting to the same thing. 
> -Razor
>  
Actually for the implementation the IUSON needs, it will not need to
inter-operate with other systems or applications.

It wouldn't be a portal site. Instead it would be used for 1 specific
function driven by the user instead of the admin user or institution.

This empowers the end user or community by giving a place to record and
store relevant medical records like short records, immunization
schedules, surgery dates, etc. Not just records from the actual
procedures.

So while we may be on the same page as far as direction in this arena it
doesn't require nearly as much effort to implement this as what you had
to implement.

But I agree LDAP integration needs to be looked at very hard. I've also
looked a bit into PAM authentication as well but that seems to be even
more complicated and OS specific. So between the two LDAP is a good way
to explore

Zoom