private SSLConfig getSSLConfigurations(Locator locator) {
    final SSLConfig sslConfig;
    if (locator == null) {
      /*
       * Locator is null in the case when a LocatorLauncher is created
       * using its Builder but start is never called, hence no locator exists.
       * Instead, this LocatorLauncher is used to get the status of the
       * locator using PID, working dir etc.
       * This is done in StatusLocatorCommand in gfsh
       */
      sslConfig = SSLConfigurationFactory.getSSLConfigForComponent(
          getProperties(),
          SecurableCommunicationChannel.LOCATOR);
    } else {
      /*
       * If a locator is already present then the DistributedConfigImpl
       * is not constructed again but rather taken from the locator properties.
       * This will avoid reading the property files and possible old address
       * verification error as those may not be valid anymore.
       */
      sslConfig = SSLConfigurationFactory.getSSLConfigForComponent(
          ((InternalLocator) locator).getConfig(),
          SecurableCommunicationChannel.LOCATOR);
    }
    return sslConfig;
  }
Returns the status of the locator on the given host and port. If you have endpoint
identification enabled the preferred method is statusForLocator(int, String), which
lets you specify the locator's name that the locator has stored in its TLS certificate

@param port the port that the locator is listening on
@param bindAddressArg the IP address to which the locator's socket binds
@return a {@link LocatorStatusResponse} representing the status of the locator
@throws IOException if there is a problem interacting with the locator
geode-core/src/main/java/org/apache/geode/distributed/LocatorLauncher.java