Discussion:
DataPower to MQ - No Security Exits, Client Channel Tables or mqclient.ini possible?
Potkay, Peter M (CTO Architecture + Engineering)
2013-08-14 11:42:45 UTC
Permalink
Looking at the latest Infocenter for DataPower, version 6 of the Firmware, there doesn't appear to be anyway to specify a client side security exit. Is SSL the only way to establish an authenticated connection from DP to MQ?

I also don't see any way of using an MQ Client Channel Table, or an mqclient.ini file.

Do the DataPower creators consciously choose not to allow for exits, channel tables and client ini files, or is this a gap that might be remediated with a Request For Enhancement? Before I take the time to write one up I wanted to check here if it even made sense. In a conversation I had with my computer screen I made the argument that maybe this is by design because exits, tables and ini files all require something to be placed ('installed' in the case of the exit) on the appliance which is a no-no. But stylesheets and SSL Certs are allowed to be placed on the appliance, so why not other stuff?

DataPower Firmware 6 Infocenter:
http://pic.dhe.ibm.com/infocenter/wsdatap/v6r0m0/index.jsp



Peter Potkay




************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Roger Lacroix
2013-08-14 15:53:07 UTC
Permalink
Hello Peter,

I asked IBM about this and at that time (4-5 years ago), they said
they did not want 3rd party code running in the appliance.

IBM made a fix (many years ago) to correctly send the UserID and
Password (in plain text) from the appliance to the queue manager. I
don't have a screen-shot but it is supposed to be under the
connection parameter settings. This is what I would suggest you use.

Regards,
Roger Lacroix
Capitalware Inc.

At 07:42 AM 8/14/2013, you wrote:
>Looking at the latest Infocenter for DataPower, version 6 of the
>Firmware, there doesn't appear to be anyway to specify a client side
>security exit. Is SSL the only way to establish an authenticated
>connection from DP to MQ?
>
>I also don't see any way of using an MQ Client Channel Table, or an
>mqclient.ini file.
>
>Do the DataPower creators consciously choose not to allow for exits,
>channel tables and client ini files, or is this a gap that might be
>remediated with a Request For Enhancement? Before I take the time to
>write one up I wanted to check here if it even made sense. In a
>conversation I had with my computer screen I made the argument that
>maybe this is by design because exits, tables and ini files all
>require something to be placed ('installed' in the case of the exit)
>on the appliance which is a no-no. But stylesheets and SSL Certs are
>allowed to be placed on the appliance, so why not other stuff?
>
>DataPower Firmware 6 Infocenter:
><http://pic.dhe.ibm.com/infocenter/wsdatap/v6r0m0/index.jsp>http://pic.dhe.ibm.com/infocenter/wsdatap/v6r0m0/index.jsp
>
>
>
>Peter Potkay
>
>
>
>
>************************************************************
>This communication, including attachments, is for the exclusive use
>of addressee and may contain proprietary, confidential and/or
>privileged information. If you are not the intended recipient, any
>use, copying, disclosure, dissemination or distribution is strictly
>prohibited. If you are not the intended recipient, please notify
>the sender immediately by return e-mail, delete this communication
>and destroy all copies.
>************************************************************
>
>
>----------
><http://listserv.meduniwien.ac.at/archives/mqser-l.html>List Archive
>-
><http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1>Manage
>Your List Settings -
><mailto:LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org?subject=Unsubscribe&BODY=signoff%20mqseries>Unsubscribe
>
>
>Instructions for managing your mailing list subscription are
>provided in the Listserv General Users Guide available at
><http://www.lsoft.com/resources/manuals.asp>http://www.lsoft.com

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Loading...