Re: CMS Using IIS Authentication

SJV Technology wrote:

> Yes, that is exactly what I mean.  Here is the problem in a nutshell.  
> We are building an intranet and need for certain pages to be 
> restricted to certain groups... (i.e. a section just for HR employees 
> or Finance employess, etc).  However, we do not... actually to be 
> perfectly honest, I am not even allowed to have the option of making 
> people login to the Intranet web site while they are within our 
> network.  These are the restrictions that I have been givien.They have 
> to be able to be automatically logged in by virtue of being logged 
> into the Domain.
>  
> This is possible with IIS integrated windows authentication.  If I use 
> this IIS authentication schema, when a person logs into a Domain 
> computer and then opens the Intranet, they won't have to log on 
> again.  The logon is passed through (they would have to logon outside 
> of our network however, but no one cares about that).  So this means 
> that any content management system I use HAS to be able to process an 
> IIS login. 
>  
> I don't care if I have to manually add users or groups to the CMS 
> itself in order ot make the authorization work.  All I care is that 
> the authentication can be passed through from IIS.  So that when a 
> user logs on via the IIS directory securty login, the CMS picks that 
> up and says "Hey, this user has logged in" and then automatically logs 
> the user into the CMS.
>  
> I have had almost no luck finding anything like this.


You may want to have a look at our HardCore web content management 
system (http://wcm.hardcoreinternet.co.uk/), which supports IIS 
authentication exactly like you described it:

You can configure IIS to require authentication to access the website. 
When the HardCore web content management system requires authentication 
(to view access restricted content or to access the web content 
management system), the web content management system will check if the 
user is already authenticated by IIS and if that user account also 
exists in the web content management system's internal user database. If 
this is the case the user is automatically logged into the web content 
management system.

So user accounts (and groups/types) must be created both in Windows and 
the web content management system's internal user database, where the 
users' access permissions to access and manage content in the web 
content management system are defined (Windows' user groups and user 
permissions are not used for access permissions/restrictions within the 
web content management system).

Disclaimer: I work for HardCore and is obviously biased towards our 
products.

Best regards,
Soren Vejrum