PermissionsException when using nexus_proxy_repository

[fletchowns]

In my recipe I have:

nexus_user "admin" do
    email "somebody@somewhere.com"
    old_password "admin123"
    password "shhh"
    action :change_password
end

nexus_proxy_repository "jboss-public-releases" do
    url "https://repository.jboss.org/nexus/content/groups/public-jboss/"
end

My chef run fails on the nexus_proxy_repository line with:

NexusCli::PermissionsException
------------------------------
Your request was denied by the Nexus server due to a permissions error. You will need to administer the Nexus or use a different user/password in .nexus_cli.

Where does nexus_proxy_repository get the credentials from?

[fletchowns]

I've also noticed the behavior is different depending on if I'm doing testing in vagrant + chef-solo vs. a real node interacting with chef-server. It seems to work fine in local testing and then fails on the real node.

[fletchowns]

@KAllan357 would this conditional ever evaluate to true? I can't figure out where default_admin_credentials_updated gets assigned to true.

[KAllan357]

Its possible this is an edge case. It has been a while since I wrote that particular bit, it could be that I was expecting this attribute to be set on the Chef Environment after you know that the password has changed.

I'd be happy to accept a change to make any of this flow a bit nicer. It might be valid to expect an encrypted databag to hold some special "Chef" user in Nexus who's creds you can us on all Chef runs. Otherwise, an alternative I've been suggesting is to abandon the LWRP style of converging a Nexus server and just using a template for the different XML files that configure your server.

[fletchowns]

Cool, thanks for the info. I'll take a stab at reworking the flow a bit.