Remote Client Authorization

Exhibitor can be enabled with authentication/security. In the standalone version this is described here: Authentication Setup. For the WAR version, standard J2EE security configuration is used. In the core/library version this will depend on the application container that you use.

An important thing to note is that Exhibitor will make remote connections to the other Exhibitor instances in the ensemble. This means that Exhibitor will need to know how to authorize a client request. For the standalone and WAR versions, this is specified via command line arguments. For the core/library version this specified via a RemoteConnectionConfiguration object.

Command Line

The realm argument specifies a realm file containing authentication details. See Authentication Setup (the —realm section) for details on this file. The remoteauth argument is: [type]:[realm-user]. “type” must be either “basic” or “digest”. “realm-user” is the user to use from the realm file. Remote connections to other Exhibitor instances will use the user/password from the real file entry that matches the realm user.

RemoteConnectionConfiguration

For the core/library version, pass an instance of RemoteConnectionConfiguration in the ExhibitorArguments. Via this object you can set Jersey ClientFilter instances. Use either HTTPBasicAuthFilter or HTTPDigestAuthFilter to specify authorization information.