If you make changes to the ssh-broker-config.xml configuration file the changes will not take effect until the Connection Broker is reconfigured. After you have reconfigured the Connection Broker, existing connections will continue to use the old configuration settings while new connections will use the reconfigured settings.
You can reconfigure the Connection Broker to the current configuration file by executing one of the following commands.
$ /opt/tectia/bin/ssh-broker-g3 --reconfig
$ /opt/tectia/etc/init.d/ssh-broker-g3 reconfig
$ /opt/tectia/bin/ssh-broker-ctl reload
For example, when a user SSHBRKR owns the ssh-broker-g3 process:
# /opt/tectia/bin/ssh-broker-ctl -a /tmp/ssh-SSHBRKR/ssh-broker reload
Under MVS, when you are running the Connection Broker as a started task:
== > s sshbrkr,f=reconfig
Copyright 2014 SSH Communications Security Corporation This software is protected by international copyright laws. All rights reserved. Contact Information
What to read next:
Reduce Secure Shell risk. Get to know the NIST 7966.
The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government. Download now
ISACA Practitioner Guide for SSH
With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community. Download now