...

shrine {
...
  hub {
    create = true
  }//hub
...
}//shrine

Add your hub's Kafka user name to shrine.conf:

shrine {
...
  kafka{
    sasl.jaas.username = "yourKafkaUserName"
  }
...
}//shrine

Tomcat will need the hub's Kafka credentials to send and receive messages in tomcat's password.conf:

TODO
shrine.kafka.sasl.jaas.password = "hubPassword"

Configure shrineNetworkLifecycle

The shrineNetworkLifecycle needs the admin Kafka credentials to create, modify, and delete Kafka topics. Add that to the shrineNetworkLifecycle's conf/override.conf and conf/password.conf :

shrine.kafka.sasl.jaas.password = "andminPassword" 

shrine.kafka.sasl.jaas.username = "andminUsername" TODO

network.conf

To use Kafka: in network.conf, specify a Kafka section with the specifics to share with downstream nodes:

shrine {
  network {
    network {
      name = "Network Name"
      hubQueueName = "hub"
      adminEmail = "yourEmail@yourhospital.edu"
      momId = "arn:aws:iam::1234567890:user/your-hub"hubUsername"
      kafka = {
	    networkPrefix = "BestNetwork"
        bootstrapServers = "YourBootstrap1:Port,YourBootstrap2:Port,YourBootstrap3:Port"
        securityProtocol = "SASL_SSL"
        securityMechanism = "SCRAM-SHA-512"
      kafka = todo}
    }
    nodes = [
      {
        name = "Hub's node"
        key = "hub-node"
        userDomainName = "network-hub"
        queueName = "hubNode"
        sendQueries = "false"
        adminEmail = "yourEmail@yourhospital.edu"
        momId = "todohubUsername"
      }
    ]
  }
}

...

Choose a network prefix. This will be prepended to queue names to allow managing multiple networks on the same Kafka cluster.

...

Note that the network's momId is the same as hub's node momId. The You - the Kafka admin - will make a Kafka account for each downstream node, and share the username and password by a secure channel.