The use of an instance of this class does not imply directly a {@link ServerAuthentication#YES} constraint; that must be specifiedseparately to ensure that the server actually authenticates itself. Because this constraint is conditional on server authentication, it does not conflict with {@link ServerAuthentication#NO}.
It is important to understand that specifying ServerAuthentication.YES
as a requirement does not ensure that a server is to be trusted; it does ensure that the server authenticates itself as someone, but it does not ensure that the server authenticates itself as anyone in particular. Without knowing who the server authenticated itself as, there is no basis for actually trusting the server. The client generally needs to specify a ServerMinPrincipal
requirement in addition, or else verify that the server has specified a satisfactory ServerMinPrincipal
requirement for each of the methods that the client cares about.
@author Sun Microsystems, Inc.
@see ServerAuthentication
@see net.jini.security.AuthenticationPermission
@since 2.0
|
|