disabling anonymous causes failures

[sfiggins]

With anonymous access disabled, some commands, like creating new users with nexus_user, or new proxies with nexus_proxy_repsoitory will fail with a permission error.

[KAllan357]

I sounds like a bug that those resources aren't using the credentials set in the data bag.

[fishnix]

@KAllan357 I get the same failure if I disable the anonymous account, but repo adds/deletes worked fine prior to the anonymous user being disabled. @sfiggins did you ever figure this out?

[sunruh]

The reason for this problem is that all resource providers check first whether Nexus is available by calling Chef::Nexus.ensure_nexus_available(node) which in turn calls Chef::Nexus.anonymous_nexus_remote, attempting to anonymously connect to Nexus.

chef_nexus.rb could be modified to have a 2nd rescue for NexusCli::PermissionsException assuming that a nexus is available in this case:

begin
[...]
rescue Errno::ECONNREFUSED, NexusCli::CouldNotConnectToNexusException, NexusCli::UnexpectedStatusCodeException => e
[...]
rescue NexusCli::PermissionsException => e
  Chef::Log.info "Could not connect to Nexus anonymously, assuming availability"
  return true
end