Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>With Windows-to-Windows connections, WMQ will pass the SID as well as the "short ID" which in this case would be "websphere". This is a little better authorization than you get with non-Windows WMQ which only uses the short ID. The problem is that someone on a non-windows server can connect using the short ID "websphere" and since there is no SID WMQ will accept the connection as thought it <em>were</em> the Windows account.</p> <p>Two ways to address this. On the QMgr host you can run setmqaut commands to authorize the SID you are actually using to connect. The VM <em>must</em> be able to inquire on the domain where the Windows account lives and the setmqaut command must use -p user@domain syntax.</p> <p>Alternatively, you can just use the locally defined ID in the MCAUSER of the channel like </p> <p>ALTER CHL(channel name) CHLTYPE(SVRCONN) MCAUSER('webaphere@vm') </p> <p>...where 'vm' is the name of the virtual machine and you've authorized the account with setmqaut commands or by putting it into the mqm or administrators group.</p> <p>Keep in mind this is <em>only</em> for testing! Any channel with a blank or administrative MCAUSER can not only administer WMQ but also execute arbitrary commands on the underlying host server. In the real world you would create accounts with access to queues and the QMgr but not access to administer and you'd put those into all MCAUSER values, then set MCAUSER('nobody') for all the SYSTEM.DEF and SYSTEM.AUTO channels.</p> <p>Lots more on this available on my web site t-rob.net in the MQ and Links pages. Also, check out:</p> <p>Comment lines: T.Rob Wyatt: <a href="http://www.ibm.com/developerworks/websphere/techjournal/0701_col_wyatt/0701_col_wyatt.html" rel="nofollow noreferrer">What you didn't know you didn’t know about WebSphere MQ security</a></p> <p>Comment lines: T.Rob Wyatt: <a href="http://www.ibm.com/developerworks/websphere/techjournal/0711_col_wyatt/0711_col_wyatt.html" rel="nofollow noreferrer">WebSphere MQ security heats up</a></p>
    singulars
    1. This table or related slice is empty.
    1. POAuthorization with Websphere MQ 6
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRivieraKid
    1. UST.Rob
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload