ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Broker keystore path problem

Post new topic  Reply to topic
 Broker keystore path problem « View previous topic :: View next topic » 
Author Message
ammx
PostPosted: Thu Jul 19, 2018 8:08 am    Post subject: Broker keystore path problem Reply with quote

Acolyte

Joined: 08 Sep 2017
Posts: 50

Hi

I created a new keystore and trustore for my broker B2BESBBKRDEV1. I needed to change some expired certificates and I didnt have the password for the old keystore, so I had to create a new one. I added the new certificates without problems and change the keystore and trustore path of the broker with the following command

mqsichangeproperties B2BESBBKRDEV1 -o BrokerRegistry -n brokerKeystoreFile -v /home/wmbadmn7/ssl

Then i restarted the broker and verified the path had changed with

mqsireportproperties B2BESBBKRDEV1 -o BrokerRegistry -r

$ mqsireportproperties B2BESBBKRDEV1 -o BrokerRegistry -r

BrokerRegistry
uuid='BrokerRegistry'
brokerKeystoreType='JKS'
brokerKeystoreFile='/home/wmbadmn7/ssl/B2BESBBKRDEV1.jks'
brokerKeystorePass='brokerKeystore::password'
brokerTruststoreType='JKS'
brokerTruststoreFile='/home/wmbadmn7/ssl/B2BESBBKRDEV1trustore.jks'
brokerTruststorePass='brokerTruststore::password'
brokerCRLFileList=''
httpConnectorPortRange=''
httpsConnectorPortRange=''
brokerKerberosConfigFile=''
brokerKerberosKeytabFile=''
allowSSLv3=''
reenableTransportAlgorithms=''
reenableCertificateAlgorithms=''
mqCCDT=''
modeExtensions=''
operationMode='enterprise'
adminMessageLogging=''
productFunctionality=''
mqKeyRepository=''
dataCapturePolicyUri='/apiv1/policy/DataCapture/default'
shortDesc=''
longDesc=''

BIP8071I: Successful command completion.

the path was successfully changed to point new keystore B2BESBBKRDEV1.jks, but somehow when i ran the vulnerability scan, the old certificates from the old keystore keep appearing. I dont know why, if i restarted and everything seemed fine

Thanks in advance
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Jul 20, 2018 9:37 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

Was that cert setup at the integration server or integration node level? or Both?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
ammx
PostPosted: Wed Jul 25, 2018 5:47 am    Post subject: Reply with quote

Acolyte

Joined: 08 Sep 2017
Posts: 50

The problem was that i had to configure the nodes with HTTPSConnector, this way:

mqsichangeproperties <broker_name> -b httplistener -o HTTPSConnector -n
keystoreFile -v <keystore file name>

instead of just:

mqsichangeproperties <Broker name> -o BrokerRegistry –
n brokerKeystoreFile -v <Fully qualified name of the new Keystore>

Once i did that the vulnerability was gone. I dont know why is that
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Broker keystore path problem
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.