dCache - a system for storing and retrieving huge amounts of data, distributed among a large number of heterogenous server nodes, under a single virtual filesystem tree with a variety of standard access methods
There are a number of issues in the release notes and/or .properties documentation about the cells plain/TLS config:
The release notes speak about the non-existent dcache.broker.core.channel.security option.
They also seem to pretty much contradict the docs in the .properites, release notes say:
to none in order to listen only for plain-text communication on dcache.broker.plain.port, to tls in order to listen only for TLS encrypted communication on dcache.broker.tls.port or to none,tls in order to listen for both plain and encrypted communication.
while .properties seem to implies that core domains listen always on plain AND tls but connect in EITHER plain OR core to other core domains:
Along with accepting cell messages on plain and tls mode, a CoreDomain
also connects to other available CoreDomains as a client. With this
property, a core domain can be configured to use one of plain-text (none)
or encrypted(tls) connections when connecting to other.
There are a number of issues in the release notes and/or .properties documentation about the cells plain/TLS config:
The release notes speak about the non-existent dcache.broker.core.channel.security option.
They also seem to pretty much contradict the docs in the .properites, release notes say:
while .properties seem to implies that core domains listen always on plain AND tls but connect in EITHER plain OR core to other core domains:
Cheers, Chris.