Secure Mobile Access 12.4 Administration Guide

Using Session Property Variables

After a user has started a WorkPlace session by logging in, there are several session properties that are known, such as the name of the community to which the user has been assigned. You can use these properties to create dynamic resources.

For example, you might want mobile users to have access to a different network share than users with desktop computers. The way you would do this is as roughly as follows:

  • Define two communities (Mobile and Desktop).

  • Set up two file shares on your network. For example, \\company\Mobile and \\company\Desktop.

  • Define a resource for WorkPlace: \\company\{Session.communityName}.

A single resource can in this manner present both kinds of users with the link that’s appropriate for their devices. Use the variables in the below table.

Built-in variables
Built-in variablesDescription
{Session.activeDirectoryDomain}The FQDN or IP address of the AD domain to use as a search base.
{Session.activeDirectoryDomain2}The FQDN or IP address of a second AD domain to use as a search base (if you’re using chained authentication).
{Session.communityName}The name of the community to which the user was assigned when he or she logged in. The community controls which access agents are available and the end point.
{Session.ntDomain}The login domain. For example, server3 in this FQDN: server3.uk.company.com.
{Session.password}The password from the first authentication method.
{Session.password2}The password from the second authentication method, if used.
{Session.qualifiedName}For your primary (or only) authentication method, this is the fully qualified user name (username@userdomain.company.com).
{Session.qualifiedName2}For your secondary authentication method, this is the fully qualified user name.
{Session.realmName}The name of the realm the user is logged in to.
{Session.remoteAddress}The IPv4 or IPv6 address of the user's host as seen by the appliance.
{Session.userName}The short name for the user from the first authentication method. The short name is usually used for both the user’s email address and home folder.
{Session.userName2}The user’s short name from the second authentication method, if used.
{Session.zoneName}The name of the zone to which the user has been assigned, based on the profile of his or her device.
{Session.ssoUserName}The user name for single sign-on.
{Session.ssoPassword}The password for single sign-on.
{URL_REF_VALUE}The value of the first variable in the URL of a shortcut.

To create a WorkPlace shortcut to a network share based on user name

  1. In the AMC, navigate to Security Administration > Resources.

  2. Click the + (New) icon.

  3. Select Network share from the dropdown list.

  4. Give this resource a name (for example, Personal Folder), and then type the UNC path for the user folders on your network in the Network share field. For example, \\marine_lab\users\.

  5. Click {variable} and select Session.userName to add a variable that represents the short login name for the user. When you click Insert, the entry for Network share looks like this: \\marine_lab\users\{Session.userName}
  6. Select the Create shortcut on WorkPlace checkbox, and then click Save. By default, the resource you created will be displayed as a link in WorkPlace titled Personal Folder. If you want to change the link text, go to the WorkPlace page in AMC, and then click the link for the new shortcut.

When the user jdoe connects to WorkPlace, the variable is automatically replaced with the name entered during login and provides access to a folder named \\marine_lab\users\jdoe. When user rsmith follows the same link, he has access to the \\marine_lab\users\rsmith folder.

Was This Article Helpful?

Help us to improve our support portal

Techdocs Article Helpful form

Techdocs Article NOT Helpful form

  • Still can't find what you're looking for? Try our knowledge base or ask our community for more help.