Broker SSL Identity and ACLs (Identify not recognized)

, , ,
1

Hello Folks,

I am using webMethods Broker 7.1.2 and My webMethods 7.1.2.

I am trying to configure the Broker for SSL and also configure Broker ACLs.

After I assign an SSL identity to the Broker Server, I am unable to access the ACL tab in the Broker Server Details page of My webMethods.

After assigning an SSL identity to the Broker Administrator user interface in My webMethods I get the following error when I click on the ACL tab:

“Broker server connection is not using SSL, possibly because of a mismatch in SSL identity. Set the correct identity on Broker server and/or Broker Administrator and return to this page.”

On the Configuration tab of the Broker Server Details page, it says “SSL is configured and working”, however it also says “Identity not recognized”.

After uploading the keystore and truststore files, here are the steps I am following:

First, assign an SSL identity to the Broker Server

  1. In My webMethods: Messaging > Broker Servers > Servers.
  2. Click the link to the Broker server
  3. Click the SSL tab
  4. Click Change Configuration
  5. Click Local Keystore tab
  6. Select Keystore with type “PKCS12”
  7. Select truststore with type “PEM”
  8. Type in Cipher Suites “All:eNULL”
  9. Select verification depth “9”
  10. Select SSL Protocol “ALL”
  11. Type in SSL Keystore Password
  12. Click Get User Names
  13. Click Apply

Then assign an SSL identity to the Broker Administrator user interface

  1. In My webMethods: Messaging > Settings.
  2. Click Identity tab
  3. Click Change Identity
  4. Type in SSL Keystore Password
  5. Click Get User Names
  6. Click Connect

By the way, I am using a self-signed certificate, could this be related to the issue?

Any help or ideas to try would be greatly appreciated, I have also raised this with SAG.

2

Hi,

was this solved ?
What was the result of the SAG ticket?

I have currently the same thing on the latest of our 9.5 Environments.
The previous 9.5 environments as well as all of our 7.1.2/7.1.3 Environments could be activated correctly.

Regards,
Holger

3

We solved this by generating new certificates for this environment.

When importing these the Broker SSL and the Identity could be enabled.

Regards,
Holger