Publishing an Android .aar to Maven Central fails on Nexus login. Outdated credentials, a result of Jira’s removal, cause a 401 error.
I recently encountered a similar situation after the discontinuation of Jira affected our credential management. Initially, I assumed it was just a simple token issue and tried updating the existing credentials, but without luck. The breakthrough came when I performed a complete audit of the Nexus settings, which revealed outdated references embedded in the automation scripts. I updated those directly in the repository configuration and also cleared any cached authentication details. This ensured that only the new token was active, which finally resolved the 401 error. Reviewing script references and environmental variables was key to solving the issue.
hey, try regeneratin your creds on nexus. had similar probs after jira got dropped. updating tokens cleared it for me. check docs for any changes
Considering similar issues in our setup, I found that the solution involved a full review of the Nexus configuration settings. After checking for any lingering references to deprecated credentials, I updated the account details directly on the Nexus administration panel rather than relying solely on the project’s configuration file. Additionally, ensure that the migration of credentials following the Jira discontinuation is complete. Clearing the cache and updating the authentication settings resolved the 401 error in our instance. It’s worthwhile to verify that no environmental overrides are using outdated tokens either.