Gradle Artifactory plugin (v4.24.16) leads to auth errors (401) when using Gradle Wrapper >= v7.x

[iwt-tobiasboehm]

Describe the bug
When we upgraded our Android Library project to Gradle wrapper v7.x something changed for the Gradle Artifactory plugin (v4.24.16) that now leads to authentication errors when uploading artifacts (unauthorized error 401). Also our infrastructure team informed us that upload tasks, that were run with a CI pipeline script using gradle 7.x wrapper (does not matter which one, we tried 7.0.2 as well as 7.2), lead to Artifactory access attempts with an anonymous user. The way username/password are provided are still the same.

Config looks like this:

artifactory {
    contextUrl = "https://xxx/artifactory"

    getClientConfig().publisher.setPublishBuildInfo(false)
    getClientConfig().publisher.setPublishArtifacts(true)

    publish {
        repository {
            repoKey = isReleaseBuild() ? "maven" : "maven-snapshots"
            username = getRepositoryUsername()
            password = getRepositoryPassword()
            maven = true
        }

        defaults {
            publishArtifacts = true
            publishPom = true
        }
    }
}

getRepositoryUsername() and getRepositoryPassword() read some env vars. However simply replacing them with hardcoded credentials doesn't change anything regarding the gradle 7 behaveiour.

We can make the plugin work again by switching back to Gradle 6.9.1, however we need to switch to Gradle 7 soon for several reasons (android compose / target SDK 30 etc.).

To Reproduce
Try to upload artifacts to an Artifactory service from an Android Library project using Gradle Artifactory plugin (v4.24.16) utilizing a publish { repository { username / password } } config running on Gradle wrapper 7.x. 

Expected behavior
Upload still works.

Versions

• Gradle Artifactory plugin version: 4.24.16
• Operating system: OS X Big Sur
• Artifactory Version: 7.3.2

Additional context
Add any other context about the problem here.

[yahavi]

@iwt-tobiasboehm,
Thanks for reporting this issue.
Unfortunately, we couldn't reproduce this issue. Would you consider creating a minimal reproducible example project on GitHub?

[iwt-tobiasboehm]

@yahavi you took an Artifactory enabled project with Gradle 6.9.1 and upgraded it to Gradle 7.x and still everything works as expected when uploading new artifacts? Do you know what might have changed regarding anything you use internally in your plugin for communicating with the Artifactory server when switching from Gradle 6 to 7?

[iwt-tobiasboehm]

Turn out the issue was a static defined method for reading the env vars. For some reason this was working fine with Gradle 6 but starting with Gradle 7 this method returned null.