Skip to content

Do Not Send Artifactory Credentials to OSS Resolution Repositories #230

Closed

Description

@jzheaux

SpringRepositoryPlugin builds a single RepositorySpec from artifactoryUsername/artifactoryPassword and applies it to spring-oss-snapshot, spring-oss-milestone, and spring-oss-release. Those are public repositories that don't need credentials, so Gradle sends them to repo.spring.io/{snapshot,milestone,release} on every resolution, and a stale credential can turn a public request into a 401.

Only the commercial repositories added by InternalRepositoryConventions should carry credentials.

Scope: dependency resolution only. Credentials are still needed for publishing, so publishing configuration must not change.

Acceptance criteria

  • The OSS repositories added by SpringRepositoryPlugin have no credentials
  • The internal/LTS repositories still receive credentials when both properties are set
  • Tests in SpringRepositoryPluginTests assert both of the above
  • The ARTIFACTORY_* property lookup lives in one place rather than being duplicated

Activity

  1. added this to the 1.1.3 milestone on Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    in: pluginAn issue related to the Gradle plugintype: bugA general bug

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions