How to restrict user access to separate ASP.NET file via Extranet security?

Topics: General, Standard packages, Troubleshooting
Jul 7, 2011 at 9:00 AM
Edited Jul 7, 2011 at 9:13 AM

For a specific project we need to be able to test – via Code Behind in a given ASP.NET file - whether or not a given user is logged on to the Extranet module.

This approach is necessary to ensure restricted access to a set of advanced forms that may only be accessed by Extranet users who are logged in. The forms are far more advanced than what may be created via the built-in C1 Form module, which is the reason why we need to be able to externally test the users login status in relation to the C1 Extranet module security.

Could this be done directly from the separate ASP.NET files Code Behind? Perhaps via testing a Session Variable set by the Extranet module? Perhaps there is a more snazzy way to test the users status directly from a separate ASP.NET file which we are not aware of?

It is imperative to emphasize that the separate ASP.NET file (and the subsequent Code Behind file) will be located on the same domain as the C1 project itself. It is actually located in a separate folder placed in the root structure which makes it directly accessible to all users unless access restrictions are implemented in order to ensure the users rightful Extranet/login status.

All suggestions will be welcomed - thank you in advance.   :o)

Jul 7, 2011 at 10:02 AM


There is the public static ExtranetFacade class which is a part of the Composite.Community.Extranet.ExtranetFacade namespace. You can read this Developer Guide to learn this class methods. Hope, you will find some helpful information.

Jul 7, 2011 at 10:10 AM

That sounds like a possible solution - thank you, Inna.  :o)