Add credential definition for Cisco enable and sudo escalation as well as Salesforce.com and Palo Alto.
Public key SSH credential definition, requiring a previously-uploaded file name.
Certificate SSH credential definition, requiring previously-uploaded user certificate and private key file names.
The SSH credential definition was getting very long and had a lot of optional parameters. I broke it up into subclasses and moved escalation fields into functions on the SSH superclass so we can use a fluent style to describe escalations. Looking through all the credentials currently supported, SSH is the most complex.
Reformat long lines
SSH sudo credential definition tests.
Documentation update for credentials changes.
Update ness_rest to make use of the credentials module.
Remove unused function _policy_set_creds(). Now all credentials are added using policy_add_creds(). Within the API there is the possibility to delete credentials from an existing policy, so I think the new name is a little more tightly named.
Instead of appending command line credentials to credentials found in the config file, allow command line values to override the config. This is the preferred behavior.
Merge remote-tracking branch 'origin/master' into additional_credentials
Merge pull request #3 from tenable/additional_credentials

Additional credentials