Allow client to specify internal authentication

The RPC client currently uses a token if present, else it falls back to authentication. This creates an ambiguity in the client if SIMPLE auth is allowed to use tokens. A task will continue to run if the task loses its tokens because it will fallback to SIMPLE auth - this would be a bug. There should be a means to specify that tasks must use tokens to avoid the ambiguity.