Run FL over secure RPCΒΆ
In this part, we describe the procedure to run federated learning experiment with authentication by running an FL server and an FL client. The following figure illustrates the gRPC communication with token-based authenticator:
As access tokens are transferred from clients to server for authentication, a secure SSL channel is required for gRPC communication to encrypt the transmitted data. In each RPC from client to server, the client will attach its authentication token as call metadata and send to the server for validation. APPFL currently supports two types of authenticators NaiveAuthenticator for demonstration purposes and GlobusAuthenticator for real deployment. Please refer to the authenticator documentation to learn more about the authenticators and how to define your own authenticator if needed.
In the following two notebooks, we will use the NaiveAuthenticator for easy demonstration, where the client simply uses hardcoded authentication tokens for validation.