Forum Discussion

Miron_du_Plessi's avatar
Miron_du_Plessi
Icon for Nimbostratus rankNimbostratus
Jun 15, 2006

Different Prelogin Inspection

Hi,

 

 

Does anyone know if it is possible to create different prelogin

 

inspections based on a user landing on a different URI, or a single prelogin inspection that runs different scans based on

 

a different landing URI or destination IP address.

 

 

The reason why I ask is because we are trying to create two fundamental different uses for the firepass.

 

 

Use1: Portal Access Only - Used by staff/students to access web

 

based resources from home. No access to Network Access,

 

and no requirement to have a prelogin inspection checking

 

for antivirus , spyware etc.

 

Use2: Portal Access and Network Access - Used by Admins and Staff

 

to allow them access to the LAN. Prelogin inspection

 

required to include Antivirus , Spyware checking etc.

 

 

If we could have a web link eg. firepass.company.com/students

 

which limited those that logged in to USE1:, and firepass.company.com/staff that allowed access to Use2:

 

 

Kind Regards

 

 

Miron du Plessis
  • Posted By mironduplessis on 6/15/2006 4:05 PM

     

     

    Hi,

     

     

    Does anyone know if it is possible to create different prelogin

     

    inspections based on a user landing on a different URI, or a single prelogin inspection that runs different scans based on

     

    a different landing URI or destination IP address.

     

     

    Miron,

     

     

    Absolutely. If you haven't received an answer yet, or figured it out, here's how you can do it (assuming that you've already built your custom URI landing pages, so they exist):

     

     

    1) Create a new blank sequence and open it for editing in the visual policy editor.

     

     

    2) Add a new inspection first that does not use one of the built-in inspectors, insert a new rule, and name it accordingly.

     

     

    3) For the rule, you'll want to take advantage of the session.network.server.land_uri user variable, documented here:

     

     

    http://devcentral.f5.com/Wiki/default.aspx/FirePass/EndPointSecuritySessionVariables.html

     

     

    You will set its evaluation value to the name of your URI, such as "students" or "teachers"

     

     

    4) Then you can push all of your existing eps checks after this very first check. So when a user logs in, the eps checks will be determined by their landing URI. Your results for this rule won't be "Allow Login" or "Deny Login", but instead will start sub-groups with your complete eps checks for your various groups.

     

     

    Another helpful tip is to enable variable logging for all users, which dumps all eps variables to the logs on successful login. This is documented in the help. WARNING, it will fill up your logs if you leave it on forever.

     

     

    Good luck!

     

     

    rcrawley

     

  • Hi,

     

     

    Thanks for that, we had worked it out already:-) Apologies

     

    I should have updated the topic.

     

     

    Regards

     

     

    Miron