You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[FAB-8350] Support different listener for admin server
The peer's admin server shares the listener with the endorser one.
This doesn't make much sense because the admin service might be deployed
in a setup where it should only be accessible to peer administrators and
not to clients, and also - mutual TLS is used, then it also accepts
TLS client certificates issued by CAs of other organizations which
share a channel with the peer's organization.
This change set makes it so that the admin server can have its own listener.
By default - it still registers to the peer's gRPC service.
However, if the listen address is specified in the core.yaml and it's port
differs from the port of the peer service - it creates its own gRPC
service and attaches to it instead of the peer's.
Change-Id: I69c132348da17cdd6e4e4f9b31ba5c59d6a3f1cb
Signed-off-by: yacovm <yacovm@il.ibm.com>
0 commit comments