Geek asks and answers

WebSphere Application Server 7.0 ignores Windows userId when connecting to MQ

Has anyone encountered a problem when WAS does not use the Windows username when connecting to the Websphere MQ resource? None of our developer mailboxes have ever encountered this problem in the past; they were able to send username via MQ for authorization. But we have a new machine for developers, which does not seem to send username, and therefore the connection to MQ cannot be made.

We tried to specify a J2C authentication alias for QCF using DefaultPrincipalMapping, but this did not work.

SOLUTION: It turned out that the problem was that the server was installed and started as a Windows service. When we created a new server profile that was started by the user, and not as a service, he used the Windows username when connecting to MQ.

+3
source share
1 answer

, , . WAS, User ID Connection Factory , WAS . WebSphere MQ , , . , WAS , . , , MCAUSER.

WAS WMQ, . - WMQ , .

, : QMgr MCAUSER. QMgr MCAUSER, MCAUSER CONNECT, . SSL SSLPEER , . ? WebSphere MQ . , WMQ . , , - , .

, , , , , , QMgr , , . D'! QMgr, , "" ID WAS. . Hardening WebSphere MQ IMPACT.

+3

More articles:


All Articles