This question is a follow-up to this archived thread. In that thread, the only suggestion for addressing a desire to restrict access to specific AR web interfaces was an exploration of creating a new IIS Site. dyannic talked about editing Web.config to define roles, etc. While considering this idea as well, this struck me as unviable, since that Web.config file would be shared by all instances of the interface.
The thought that I've had was to create a symlink folder (e.g., C:\Program Files\One Identity\Active Roles\7.5\Web\RestrictedSite) that is a link to "C:\Program Files\One Identity\Active Roles\7.5\Web\Public". Even though the "RestrictedSite" link folder is just a redirect to the "Public" folder, it does allow separate NTFS permissions to be assigned, meaning that I can create multiple sites pointing to the same directory with different sets of permissions. Initial testing seems to suggest that this will work; I was just wondering if anyone else might have tried this and had any success or failure?
Thanks very much,
Shawn.