Checking the password for a resource that is used by an integration node

To check what security credentials are set on an integration node that is connected to a remote system or database, use the mqsireportdbparms command.

About this task

If you have an integration node that accesses external resources, you can check what security credentials are set if a security identity was created for the integration node. For more information, see Security identities for integration nodes connecting to external systems.

You can check whether a password is valid for a set of security credentials. You might want to check a password if you recently updated the password while the integration node was running, to see whether the new password is in effect.

To review the security credentials that are set for a resource that is connected to an integration node, complete the following steps.

Procedure

Run the mqsireportdbparms command with the name of the integration node that you want to check in the following format:
  • If you are connecting to an SFTP data source:
    mqsireportdbparms -n IBNODE SFTP::server -u user_id -i SSH_identity -r password
  • If you are connecting to a non-SFTP data source:
    mqsireportdbparms -n IBNODE userdb -u user_id -p password

Where the names represent:

  • IBNODE as the name of your integration node
  • server as the details of your SFTP connection
  • SSH_identity as the SSH connection name
  • userdb as the data source name
  • user_id as the user ID that you want to check
  • password as the password that you want to check is valid for the integration node

If you specify the integration node name only, then the command returns if any security credentials are associated with that integration node.

Results

A result is returned that confirms whether the password that was provided is correct, or if it was incorrect. If there are no security credentials set for that integration node, then an information message is displayed.

Additionally, the command returns if the integration node was restarted after a password change, so that you know what password is valid for the integration node while it is running.