Configuring the user context that is used for authorization in the messaging REST API
You can configure what user context is used for authorization when you
are using the messaging REST API to send, receive, browse, or
publish a message. That is, you can choose whether the user that is logged in to the messaging REST API, or the user that started the mqweb server, is used
for authorization.
Before you begin
To complete this task, you must be a user with certain privileges so that you
can use the dspmqweb and setmqweb commands:
On z/OS®, you must have authority to
run the dspmqweb and setmqweb commands, and write access to
the mqwebuser.xml file.
On all other operating systems, you must be a privileged user.![[Linux]](../common/../configure/nglinux.gif)
If the mqweb server is part of a stand-alone IBM® MQ Web Server installation, you must have write access to the
mqwebuser.xml file in the IBM MQ Web Server
data directory.
Attention:
Before you issue either the setmqweb or dspmqweb commands on z/OS, you must set the WLP_USER_DIR environment variable so that the variable points to your mqweb server configuration.
To set the WLP_USER_DIR environment variable, issue the following
command:
export WLP_USER_DIR=WLP_user_directory where
WLP_user_directory is the name of the directory that is passed
to crtmqweb. For
example:export WLP_USER_DIR=/var/mqm/web/installation1For more information, see Create the mqweb server.
About this task
- When the user ID that is used is the user ID that is logged in to the messaging REST API, the MQMD.UserIdentifier is set to the user ID that is logged in to the REST API. The MQMD.AppIdentityData is set to the user ID that is logged in to the REST API.
- When the user ID that is used is the user ID that started the mqweb server, the MQMD.UserIdentifier is left blank. The MQMD.AppIdentityData is set to the user ID that is logged in to the REST API.
See MQMD for more information on the message descriptor parts of the IBM MQ message.