Remote User Identification Workflow Event

If you use a method of capturing actual usage from a remove program, such as CAR, the Calpendo Activity Recorder, then when somebody logs in to a remote computer, a message will be sent to Calpendo with information the user that's logged in. Depending on how the login is performed, Calpendo might receive a Windows user name. We then need to map that to a Calpendo user. The default will look for a local user with the same login name as the remote user. But you may need to do something different.

 

That's what this workflow is for: it provides an opportunity to identify who is using a remote system by the information we receive. The event provides all the information given to it, and you can then use that to calculate the Calpendo user involved.

Event Properties

There are no properties you can set on the event beyond the standard properties that can be set on all events.

Properties Available for Child Actions To Use

The following properties are available for use in any child or descendant action:

 

Property

Type

Description

ipAddress

String

The IP address that the request appears to be coming from. Depending on the nature of the networks between the instrument and Calpendo, this might not be the IP address the instrument believes it has, but it could be the IP address of a network router.

declaredIpAddressesCSV

String

A comma-separated list of the IP addresses being declared by the remote system. This will be IP addresses as used by all of its network devices.

declaredIpAddresses

Set of String

A set of the IP addresses being declared by the remote system. This will be IP addresses as used by all of its network devices.

hostname

String

The name by which the remote server knows itself.

osDomainName

String

The name of the computer domain used by the remote user.

ipAddress

The apparent IP address of the request.

loginName

String

The login name used by the user on the remote system.

result

Biskit

A biskit which contains the only part of this event's data that you should modify. The result biskit contains a single property, user which you should set to the user that you have identified.