There are two solutions to solve this:
1) Add the (remote) certificate to the keyring (like with selfsigned
certificates)
2) Use a Certificate Name Filter (CNF) to map the DN to a user ID. _________________ Peter Smit
LaSalle Bank Corporation, member of ABN AMRO NV Group
Posted: Wed Sep 29, 2004 7:50 am Post subject: Another Option
Novice
Joined: 08 Jan 2004 Posts: 21 Location: New York
Hi
I'm working with this stuff and saw this post. There is another option. We have thousands of inbound MQClient connections where the certs are not on the mainframe. On the z/OS SVRCONN channels, we are using MCAUSER instead of the CNF's. To prevent the inbound client certs from using the ID of the CHIN (which carries some authorities), we created a generic MQCERT ID that gets associated with all inbound client certs. The MQCERT ID has no authorities. You can use MCAUSER and SSLPEER to grant other mq authorities.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum