Forum Discussion
Mike_Maher
Nimbostratus
NimbostratusLanding URI in Pre Logon
I have created a couple landing URI's on Firepass and in the pre logon sequence I want to do different things depending on which URI you hit. For example, I am having a file download URI that I do not want Protected Workspace applied for, but if you hit the main site or a different URI I want PWS applied. I have tried to add a New Action with a Defined Custom Variable of session.network.server.landing_uri = "download" but then a rule that says the same but it does not seem to be working. Can you help me on how this works.
psilvasAltostratus
Hi Mike~
Customization per landing URI is a feature currently being targeted for a future release. Have you looked at virtual host customization? It is the tab right next to the Global Customization where you enabled WebDAV.
Mike_MaherI had this working at one point and I just can't remember the exact flow to the pre-logon sequence. There is a variable for pre-logon that is session.network.server.landing_uri and I just need to know how to incoporate it properly. All I want it to do is to check the landing URI at the beginning of the the prelogon and so if the user types in https://mysite.com/antivirus that it goes directly to the logon page, if they type https://mysite.com they go through the normal checks that we do and get dropped into PWS. I am almost positive I had something like this working before.- You should not use "Define Custom Variable" agent as it's function is to generate a new variable, not to do comparision of the existing ones
You need to add a new RULE to a new or any existing action so you will have yet another branch
the expression for this rule will be
session.network.server.landing_uri == "download" - Interesting, as I have this setup exactly as this, and the session.network.server.landing_uri session variable stays set at standard. When is this variable set?
- brendan_102904Its set by creating Landing URIs and then visiting them.
Create 2 Landing URIs : Test1 and Test2 under Device Mgmt > customization > URI based customization.
Now go to yourfirepass.com/test1 (note that there is no trailing slash.) The Firepass will set your landing URI to test1. This can be evaluated and acted upon in Prelogon inspection by creating a Rule(not an action) as follows:
session.network.server.land_uri == "test1" (note that the variable name is land_uri NOT landing_uri.)
If you have modified your index.html in the sandbox, you will need to place redirect index files in your landing URI virtual directories. My Firepasses have a custom splash page that does not have a login form. Clicking one of the links goes to landing URI myfirepass.com/test1 and the other goes to /test2. I created 2 directories in the sandbox called "test1" and "test2." Each has an index.html that simple redirects to myfirepass.com/my.activation.php3, which kicks off the prelogon inspection sequence. The first phase of this is to evaluate the landing uri as described above. Based on landing uri, different checks are performed, and users are then mapped to different resource groups based on AD authentication and landing URI.
Hope that helps. 
David_SimmonsI'm doing this currently, but wondered if it was possible to create a decision box based on multiple landing URI's...
For example I have landing URI's U1, U2, U3, and U4. Can I create a decision box that basically returns the landing URI and branches based on that instead of if URI=="U1" do this, if URI=="U2" do this, etc?
