Using SMH with secured and non-secured Broker

, ,
1

Hi all :lol:
I’m bringing a qustion for one of my customers.
How (if it’s even possible) can they monitor from the same SMH 2 remote brokers, when one is secured(with EntireX Security), and the second isn’t ?
Does anyone use this configuration ?
Thanks
Mona

2

I have done this. However, I did not do anything special.

My SMH is running on Windows XP. My remote brokers are running on z/OS 1.4. I have EntireX Security installed on both platforms.

When you define the remote broker (secured or unsecured) you should Set User Credentials before you try to access the remote broker. For the secured remote broker it is important that you provide a valid user id and password. I thought that you might have to add the following to the broker attribute file on the unsecured remote broker “IGNORE-SECURITY-CONSISTENCY=YES” but now I don’t think that it is necessary. I am accessing 3 unsecured remote brokers and 2 secured remote brokers. One of my unsecured remote brokers does NOT have the setting above and I can still access it via SMH.

Wayne Campos

3

Hello Wayne,
I’m well aware of the IGNORE-SECURITY-CONSISTENCY parameter- I wouldn’t like to use it .
On the Pc machine you’re using for the SMH did you install EntireX with security ?
In my case connecting the secure Broker (after setting of course user credentials) gives the message “PASSWORD NOT AUTHORIZED” :oops: and I’m passing the correct password for sure …

4

Mona,
IGNORE-SECURITY-CONSISTENCY allows a secured application to talk to an unsecured Broker. It does not compromise your security. Could you please explain why you wouldn’t like to use it?

Yes, I have EXX721 with security installed on WinXP Pro SP2 talking to EXX711 with EXS711 on z/OS.

I think that if security is not installed on your PC, or if it is installed incorrectly, PASSWORD NOT AUTHORIZED is the message you would receive.

The password is encrypted before it is sent to the Broker and then it is decrypted by the Broker. If security is not installed (or installed incorrectly) on the client then the decryption process gets the wrong value since the password was not encrypted properly on the client.

Wayne

5

Thanks Wayne.
I’ll try this way :slight_smile:

6

Hi Mona,

It seems the client has to be on EXX721 to make this work without the IGNORE-SECURITY-CONSISTENCY parameter set to YES.

In EXX721 there is a new ACI field named KERNELSECURITY.

Description about KERNELSECURITY from the 721pl15 documentation:

It has two purposes:

  • First – this field tells you (function KERNELVERSION) whether you communicate with a secure or non-secure Broker.

    Second – you can specify (functions other than KERNELVERSION) the behavior you request regarding security (security or no security) for your call.