JENKINS prompts "Invalid Username Password" in Enable Nexus Pro support

Hi All

We are in the process of upgrading our Jenkins version and as a best practise we have created test environment. We use “Nexus Pro support” to close staged artefacts in the Nexus. The live environment behaves as intended while the test environment fails.

Following are the environment details;

Jenkins: 2.346.3
Nexus : 2.14.10-01

We can clearly see that the artefacts are pushed to nexus from the test environment but are “open” in the nexus end. AFAIK, we use NEXUS PRO to automatically change the state to release in the Nexus.

Does anyone use NEXUS PRO SUPPORT in Jenkins and know why this is occurring?