RFHUTIL CONNECTION STRING PASSWORD
MQ administrators are required to provide a userid and password in this instance. QMNAME(QM_80) CONNAUTH() 2) The authoinfo object has a value of REQDADM for the attribute CHCKCLNT. The errors indicate the following: 1) The queue manager has a connection authority attribute called: CONNAUTH and the value for this attribute is: display qmgr CONNAUTH 9 : display qmgr CONNAUTH AMQ8408: Display Queue Manager details. This message accompanies a previous error to clarify the reason for the user ID and password check. EXPLANATION: The user ID 'rivera' and its password were checked because the user ID is privileged and the queue manager connection authority (CONNAUTH) configuration refers to an authentication information (AUTHINFO) object named '' with CHCKCLNT(REQDADM). When the userid and password are not supplied or the password is incorrect, then the following error is displayed (the error AMQ5542 is very similar): AMQ5541: The failed authentication check was caused by the queue manager CONNAUTH CHCKCLNT(REQDADM) configuration. CauseIn MQ 8.0, a new function is introduced that requires MQ administrators using remote access to supply the userid and password. EXPLANATION: The call to initialize the User ID 'rivera' failed with CompCode 2 and Reason 2035. 06:33:10 - Process(16728.4) User(rivera) Program(amqrmppa.exe) Host(HOST_A) Installation(Installation3) VRMF(8.0.0.0) QMgr(QM_ANG8) AMQ9557: Queue Manager User ID initialization failed for 'rivera'. You can amend the CHCKCLNT attribute in the CHLAUTH record, but you should generally not allow unauthenticated remote access. To avoid the authentication check, you can either use an unprivileged user ID or amend the authentication configuration of the queue manager. For example, the local operating system user database or an LDAP server. The authentication configuration of the queue manager connection determines the user ID repository. Ensure that a password is specified by the client application and that the password is correct for the user ID. ACTION: Refer to the previous error for more information.
06:33:10 - Process(7512.22) User(rivera) Program(amqzlaa0.exe) Host(HOST_A) Installation(Installation3) VRMF(8.0.0.0) QMgr(QM_ANG8) AMQ5541: The failed authentication check was caused by the queue manager CONNAUTH CHCKCLNT(REQDADM) configuration. ACTION: Ensure that the application provides a valid user ID and password, or change the queue manager configuration to OPTIONAL to allow applications to connect which have not supplied a user ID and password.
There are 3 errors: 06:33:10 - Process(7512.22) User(rivera) Program(amqzlaa0.exe) Host(HOST_A) Installation(Installation3) VRMF(8.0.0.0) QMgr(QM_ANG8) AMQ5540: Application 'Sphere MQ\bin64\amqsputc.exe' did not supply a user ID and password EXPLANATION:The queue manager is configured to require a user ID and password, but none was supplied. SymptomTo find out more details, view the error log for the queue manager. You expected that the issue with the channel authentication records had been addressed.
RFHUTIL CONNECTION STRING CODE
This behavior is documented in the following technote: WMQ 7.1 / 7.5 queue manager RC 2035 MQRC_NOT_AUTHORIZED or AMQ4036 when using client connection as an MQ Administrator You try to remotely access the queue manager as an MQ administrator and you get the return code 2035 MQRC_NOT_AUTHORIZED. To gain access an administrator can either set the queue manager attribute CHLAUTH to DISABLED, or add the appropriate records to allow remote access. You are aware of the default behavior for the channel authentication records in which an MQ administrator cannot remotely access the queue manager. You can access the queue manager by using WebSphere MQ Explorer or MQ client applications in bindings mode. Technote (troubleshooting) Problem(Abstract)As an MQ administrator you create a new queue manager in WebSphere MQ version 8.0.
0 kommentar(er)
