How client redirection works
Redirection occurs during the Sign On process but prior to Sign On. The desktop app sends several properties to the server when attempting to sign on. These properties, which correspond to User Attributes, are compared to the values set in the redirection rules. When there is a match, redirection instructions in the rule are processed.
When redirection is ignored for a client, an informational record is written to the diagnostic log.
Client property | Description |
|---|---|
Machine IP | IPv4 address of the machine. (Windows desktop app versions from 7.0 may not pass the IP address of the machine.) |
Machine Name | Computer name. |
OS User Name | User's machine login name. |
OS Domain Name | Domain name which the machine is logged in to. |
Redirection can be to a different organization in the system, or to a different system and organization.
The Desktop Software Authentication mode must be the same in both organizations.
The Collect Workstation Info option in
Settings
> Desktop App
> General
must be enabled in the desktop app gateway of the source organization. The Create New User if an Account is Not Found option in
Settings
> User Authentication
> Assign Authentication Methods to Applications
must be enabled in the target organization.Redirection during first time sign on
For redirection across systems, redirection is logged in the end user's properties on organization 1. A user is created in organization 1.
For redirection in the same system, redirection is logged in the user's properties in the new organization. A user is not created in organization 1.
Redirection after first time sign on
For redirection across systems, redirection is logged in the end user's properties in the "from" organization.
For redirection in the same system, redirection is logged in the end user's properties in both the "from" and the "to" organizations.