The session in which commands are entered and their results displayed is the 'command' session.
The sessions in which files and directory listings are transferred are the 'data' sessions.
A command session contains no files, ever. However, it will contain file names. A data session will contain no file names, nor anything else other than the constituent bytes of files themselves (note that files do not contain their own names).
For example, an FTP session between A and B:
User at A opens an FTP session to server at B - this is the command session. The user logs in, and issues the command "get helloworld.exe". A separate, distinct session opens up between A and B in which the bytes consisting of the requested file are transferred - this is the data session. The user then logs out.
There are two sessions:
Session 1
service: 21
action: login
username: userA
password: password
action: get
filename: helloworld.exe
extension: exe
link: (see below)
Session 2
fingerprint: windows_executable
Session 1, the command session, contains the filename. Session 2, the data session, contains the file.
A feature request has been added for this
Related Articles
What does suffix mean in the FTP agent configuration 18Number of Views How to collect data from a .csv file on a password protected FTP server in RSA Identity Governance and Lifecycle 7.0.0 66Number of Views After an upgrade, uploading and downloading files to a Hardware Appliance using FTP fails on RSA Identity Governance & Lif… 34Number of Views Generating an Identity Source User Dependency Report for Authentication Manager 8.6 and above 489Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide