Search

Operator Guide

Operator Guide

10.5.3
- 10.5.0
- 10.4.0
- 10.2.3
- 10.2.2 HotFix 1
- 10.2.2
- 10.2.1
- 10.2

Back Next

MFT Web User Properties

MFT Web User Properties

Create an MFT Web User so that partners can access Informatica Managed File Transfer hosted servers to exchange files. When you define an MFT Web User, specify the user authentication properties and contact details.

The following table describes the properties in the

Basic

tab:

Property	Description
Username	Name of the MFT Web User.
Status	Status of the MFT Web User. The MFT Web User can be enabled or disabled.
First Name	The MFT Web User first name.
Last Name	The MFT Web User last name.
Email Address	The primary email address of the MFT Web User. An email address should be specified if the MFT Web User receives email communication for account creation, password reset, forgot password or they have access to Secure Mail.
Description	The description is optional information pertaining to the MFT Web User. This field is limited to 512 characters.
Organization	The company or organization which the MFT Web User belongs to.

The following table describes the properties in the

Authentication

tab:

Property	Description
Login Method	Specify which technique should be used to authenticate the MFT Web User. Valid methods are Active Directory (AD), LDAP, LDAP Managed Server, and Native.
Password Generation	Passwords for MFT Web User accounts can be generated automatically based on the MFT Web User Password Policy. Otherwise the MFT Web User Manager creating the account can manually specify a password. If specifying the password, you are alerted if the password does not meet the MFT Web User Password Policy. The maximum password length is 20 characters.
Authentication Type	The Authentication Type can be specified per service. For example, an MFT Web User can be forced to use a Password and Certificate when authenticating to FTPS but only require a Password for HTTPS. If a certificate is used for authentication, the Client Authentication setting on the SSL tab of the specific service must be set to Optional or Required. If certificate authentication is specified and the certificate being used is either self-signed or signed by an untrusted Certificate Authority (CA), then the certificate will need to be imported into the Default Trusted Certificates Key Store. Importing the certificate instructs Informatica Managed File Transfer to trust this source. If the certificate being used is already signed by a trusted authority (for example, Verisign, GoDaddy, Equifax, etc.) the certificate does not need to be imported since the trust is inherited. The following options are available: HTTPS Password - MFT Web Users login using their standard MFT Web User name and password. Certificate - MFT Web Users are authenticated by a certificate which must be in the Informatica Managed File Transfer Default Trusted Key Store and on the MFT Web User's local computer. This method does not require the MFT Web User to specify a user name or password any time they use Informatica Managed File Transfer. On enabling the Certificate authentication type, select the Digest Algorithm , and enter the corresponding fingerprint for the Web User's certificate in the box. Each MFT Web User must have a unique SHA1 Fingerprint. You can select one of the following digest algorithm: SHA1 SHA224 SHA256 SHA384 SHA512 Either - If a matching certificate is found during the connection, the MFT Web User will automatically authenticate. However if a match is not found, the MFT Web User can still login to the Informatica Managed File Transfer server with a user name and password. If Either is selected, type the unique SHA1 Fingerprint for the MFT Web User's certificate in the box. AS2 Password - MFT Web Users login using their standard MFT Web User name and password. Certificate - MFT Web Users are authenticated by a certificate which must be in the Informatica Managed File Transfer Default Trusted Key Store and on the MFT Web User's local computer. This method does not require the MFT Web User to specify a user name or password any time they use Informatica Managed File Transfer. On enabling the Certificate authentication type, select the Digest Algorithm , and enter the corresponding fingerprint for the Web User's certificate in the box. You can select one of the following digest algorithm: SHA1 SHA224 SHA256 SHA384 SHA512 Either - If a matching certificate is found during the connection, the MFT Web User will automatically authenticate. However if a match is not found, the MFT Web User can still login to the Informatica Managed File Transfer server with a user name and password. If Either is selected, type a SHA1 Fingerprint for the MFT Web User's certificate in the box. Password and Certificate - MFT Web Users are authenticated by their standard MFT Web User name and password along with a shared certificate that is both on the Informatica Managed File Transfer server and the MFT Web Users' local computer. Type the certificate's SHA1 Fingerprint in the box. FTPES (Explicit SSL) Password - MFT Web Users login using their standard MFT Web User name and password. Certificate - MFT Web Users are authenticated by a certificate which must be in the Informatica Managed File Transfer Default Trusted Key Store and on the MFT Web User's local computer. This method does not require the MFT Web User to specify a password any time they use Informatica Managed File Transfer. On enabling the Certificate authentication type, select the Digest Algorithm , and enter the corresponding fingerprint for the Web User's certificate in the box. You can select one of the following digest algorithm: SHA1 SHA224 SHA256 SHA384 SHA512 Either - If a matching certificate is found during the connection, the MFT Web User will automatically authenticate. However if a match is not found, the MFT Web User can still login to the Informatica Managed File Transfer server with a user name and password. If Either is selected, type the certificate's SHA1 Fingerprint in the box. Password and Certificate - MFT Web Users are authenticated by their standard MFT Web User name and password along with shared certificate that is both on the Informatica Managed File Transfer server and the MFT Web Users' local computer. Type the certificate's SHA1 Fingerprint in the box. FTPS (Implicit SSL) Password - MFT Web Users login using their standard MFT Web User name and password. Certificate - MFT Web Users are authenticated by a certificate which must be in the Informatica Managed File Transfer Default Trusted Key Store and on the MFT Web User's local computer. This method does not require the MFT Web User to specify a password any time they use Informatica Managed File Transfer. On enabling the Certificate authentication type, select the Digest Algorithm , and enter the corresponding fingerprint for the Web User's certificate in the box. You can select one of the following digest algorithm: SHA1 SHA224 SHA256 SHA384 SHA512 Either - If a matching certificate is found during the connection, the MFT Web User will automatically authenticate. However if a match is not found, the MFT Web User can still login to the Informatica Managed File Transfer server with a user name and password. If Either is selected, type the certificate's SHA1 Fingerprint in the box. Password and Certificate - MFT Web Users are authenticated by their standard MFT Web User name and password along with shared certificate that is both on the Informatica Managed File Transfer server and the MFT Web Users' local computer. Type the certificate's SHA1 Fingerprint in the box. SFTP Password - MFT Web Users login using their standard MFT Web User name and password. Public Key - MFT Web Users use a public key on the server to encrypt a session key that produces a secure login. Either - If a matching public key is found during the connection, the MFT Web User will automatically pass authentication. However if a key match is not found, the MFT Web User can still login to the Informatica Managed File Transfer server with a user name and password. Password and Public Key - MFT Web Users must login using their MFT Web User name and password along with a public key.

The following table describes the properties in the

AS2

tab:

Property	Description
AS2 ID	The AS2 ID of the MFT Web User. The AS2 ID is case sensitive and can be 1 to 128 ASCII printable characters in length.
Signature Certificate Alias	This is the alias of the public certificate used by this MFT Web User to sign their messages. If the certificate is signed by a certificate authority (for example, Verisign), this field can be left blank since the certificate chain already exists in the Default Trusted Certificates Key Store. If a specific certificate is to be used by the Web User for signing messages or they use a self-signed certificate, then that certificate should be imported into the Default Trusted Certificates Key Store. For more information, see the Informatica Managed File Transfer Guide .
Default Upload Folder	The location where AS2 messages are saved when received (uploaded). The default location is the default home directory for the MFT Web User, which is the [installdirectory]/userdata/webdocs/[webuser] folder, where [installdirectory] is the installation directory of Managed File Transfer and [webuser] is the account name of the Web User.
When File Exists	The action that Informatica Managed File Transfer performs when a file with the same name already exists in the default upload folder.
Require Encryption	This option indicates whether or not messages sent by this MFT Web User must be encrypted.
Require Signature	A signed message contains a digital signature from the sender to further authenticate the message. If signatures are required, any unsigned message sent by this MFT Web User will be rejected.
Require Authentication	Require username/password or certificate authentication for messages uploads. If authentication is not required, Informatica Managed File Transfer will use the AS2 ID to identify the Web User. Informatica recommends you set the 'Require Signature' option to 'true' when authentication is not required.
Asynchronous MDN Approval	If a return receipt is requested by the MFT Web User, select if the MDN will be sent automatically during the MFT Web User session or manually after the message is processed. A manual receipt can only be sent if a message is received successfully. If an error occurs during transmission, an asynchronous receipt is sent automatically.

The following table describes the properties in the

SSH Keys

tab:

Property	Description
Name	The name identifies the SSH key. The maximum length of the name is 64 characters.
Algorithm	The algorithm to use when generating the key. Valid values are RSA and DSA. It is generally recommended to use RSA.
Key Size	The length (in bits) of the key. Valid values are 512, 1024, 2048 or 4096 bits. Large key sizes will provide strong protection, but will slow the performance of encryption/decryption processes.
Fingerprint	This is the password that protects the private key portion of the SSH Key Pair and should be recorded in a safe place.
Public Key Format	The format in which to store the public key. Valid values are OpenSSH or SecureShell. It is generally recommended to use OpenSSH unless your trading partner dictates otherwise. Private Keys and passphrases should be kept confidential and should NOT be shared with trading partners.
Comments	A description to store with the key. This typically should contain the name of your organization (for example, "ABC Company SSH Key"), which will allow others to quickly identify the key.
Created By	The name of the user that created the SSH key.
Created On	The date that the user created the SSH key.

The following table describes the properties in the

Upload Restrictions

tab:

Property	Description
Allow Files with No Extension	Select this option to allow web users to upload files that don't have extensions.
Allow Files with an Extension	Select this option to allow web users to upload files that have extensions. The web users must enter the file extensions in the File Extension Filter field.
File Extension Filter	The file extension filter can permit all files, restrict specific extensions or permit specific extensions. To specify the file types web users can or can't upload, enter the file extensions in this box. Enter extensions without periods (.), separate them with commas, and don't add line breaks or spaces. For example, to allow .txt, .xls, .xlsx, and .csv files, enter txt,xls,xlsx,csv. The maximum number of characters for this field is 2,000.
Case Sensitive	Select this option to specify that file extensions are case sensitive.

Managed File Transfer Web Users

Watch

Comments

0 COMMENTS

We’d like to hear from you! Log in to comment.