We have two parent portals  running from one instance of DotNetNuke. I decided to create 2 app pools, one for each parent portal and 2 virtual folder (alias portalA and portalB). I am a little bit confused how to configure authentication in IIS for each virtual folder in one instance (portal A have anonymous access; portal B should have limit access by User Group).
How to restrict access to the pages on Parent Portal to specific users. Is it possible to implement authorization via authentication in IIS.

I mean, How to restrict access to the pages on PortalB for some users, which have access to PortalA (user have access to the default.aspx in the root folder of the DNN instance (via anonymous access)). How to restrict access to the same default.aspx in the PortalB.

Example:
IIS 

Virtual directory   Physical path for IIS    Domain                        Authorized UserGroup
PortalA                  c:\www\dotnetnuke\    www.portalA.com       UserGroupA, UserGroupB   
PortalB                  c:\www\dotnetnuke\    www.portalB.com      UserGroupA

DotNetNuke
Portals    Alias
1              www.portalA.com
2              www.portalB.com


    








 

roles and roles assignements are always provided per portal, i.e. a user, who has access to both portals in your installation, may have different roles assigned, which may be granted different permissions for pages. On each page you specify the (portal specific) roles and users to be granted view and/or edit permission, same for modules.
Note: This is not related to physical access to default.aspx. On IIS web site configuration, anonymous users need read access for the DNN install directory.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN