This setting is important for Macro user assignment as well as User-Based Licensing. If, when testing the Macro functionality in FVTerm, you see that the recognized user is not what is expected, this setting is probably what needs to be changed.
There are two major modes of licensing for Flynet Viewer concurrent (non-pooled) sessions.
| Session-Based Licensing: | Sessions are allocated and released without any identification of the user or device |
| User-Based Licensing: | Sessions are allocated and released based on identified users/devices with a maximum number of sessions allowed for each user/device |
For Session-Based Licensing, this setting is important for macro user name assignment. For User-Based licensing, since there are a variety of methods of identifying an HTTP client, a setting is necessary to manage how a user or device is identified.
Supported Values:
|
(default) -- No identity is setup for a new connection: sessions are allocated and released based on a simple maximum licensed number of sessions, regardless of user id or address |
HTTP Context User |
For custom security / identity frameworks, including SAML 2.0, Google ClientID and OAuth2 OpenID Connect.
In the past, this would work for Azure Active Directory but for AzureAD use the Claims Principal setting.
Will use the HTTPContext.user value to identify the connected user. |
Claims Principal |
For Azure Active Directory (and perhaps other AD frameworks), use this and then set the Identity Claim Type to select which property / claim to use. |
Windows Security / Active Directory |
New sessions are identified and allocated based on the connecting, logged-in Windows User. For each licensed customer in this model, there is a maximum concurrent users and maximum number of sessions that each user can connect to. |
Device IP Address |
The connecting device's IP address will be used to uniquely identify the device. For each licensed customer in this model, there is a maximum concurrent devices and maximum number of sessions that each device can connect to.
Note that if any users are behind network gateways with Network Address Translation (NAT), the gateway must support including the users local address in the HTTP headers in order to uniquely identify the user. |
