MQSeries.net :: View topic - FileInputNode-The remote user identifier supplied is invalid

Vinayak.Satapute · Posted: Mon Mar 22, 2010 11:17 pm Post subject:

Hi All,

I am trying to do a FTP get on a file present on an AIX server using FileInput Node. My broker version is 6.1.0.6.

Following is the mqsisetdbparms command I used to create the securityIdentity for the server.

mqsicreateconfigurableservice WBRK61_DEFAULT_BROKER -c FtpServer -o EAI03 -n serverName -v eaisrvr.mas.com:21

mqsisetdbparms WBRK61_DEFAULT_BROKER -n FtpServer::EAI03_ID -u myuser -p mypasswrd

mqsichangeproperties WBRK61_DEFAULT_BROKER -c FtpServer -o EAI03 -n securityIdentity -v EAI03_ID

But when I run my Message Flow I see the following warning message present in the system log.

***********************************************************
( WBRK61_DEFAULT_BROKER.default ) File node ''FileInput'' in message flow ''MyApplicationFlow''. The remote user identifier supplied as ''EAI03_ID'' is invalid.

The user identifier supplied by a securityIdentity is not valid. Either the user identifier is missing, or no securityIdentity definition exists. FTP processing for this node has been disabled.

Ensure that the securityIdentity is correctly defined using the mqsisetdbparms command. If you modify this definition, restart the message flow to pick up the new values. The message flow FTP processing will be re-enabled automatically. For more information, see the "FtpServer configurable service properties" topic in the WebSphere Message Brokers information center.
***********************************************************
Following is mqsiconfiguarble service created.

C:\Program Files\IBM\MQSI\6.1>mqsireportproperties WBRK61_DEFAULT_BROKER -c FtpServer -o EAI03 -r

FtpServer
EAI03
accountInfo=''
cipher=''
compression=''
connectionType=''
knownHostsFile=''
mac=''
protocol=''
remoteDirectory=''
scanDelay=''
securityIdentity='EAI03_ID'
serverName='eaisrvr.mas.com:21'
strictHostKeyChecking=''
transferMode=''

Appreciate your help in this issue. (is it anything to do with broker 6.1.0.6 version for any possible bug.)

Regards,
vinayak satapute