authentication

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Use org.gradle.api.credentials.PasswordCredentials internally

org.gradle.api.artifacts.repositories.PasswordCredentials was where PasswordCredentials originated before being moved to org.gradle.api.credentials package together with other Credentials implementations.

After this change org.gradle.api.artifacts.repositories.PasswordCredentials will remain to be used only in the public APIs around repositories.

Once its surface area is reduced, we might be able to deprecate it in favor of org.gradle.api.credentials.PasswordCredentials in a subsequent change.

  1. … 15 more files in changeset.
Support HTTP header based authentication for Maven repositories

Now it's possible to use a custom HTTP header to authorize access to

Maven repositories. This enables Gradle to access private GitLab and TFS

repositories used as Maven repositories or any OAuth2 protected Maven

repository.

Resolves #5571.

    • -0
    • +31
    ./DefaultHttpHeaderAuthentication.java
  1. … 30 more files in changeset.
Merge pull request #690 from kiddouk:story/S3-repository-can-be-configured-to-authenticate-using-AWS-EC2-instance-metadata

S3 repository can authenticate using AWS EC2 instance metadata

* This is related to https://github.com/gradle/gradle/blob/c2dc9979706e6b3beca13f1de860834e9255fb1b/design-docs/finding-and-using-credentials.md#story-an-s3-repository-can-be-configured-to-authenticate-using-awss-ec2-instance-metadata

* Note that the AWS S3 Client implementation will now use the following

credentials (in this specific order)

- Environment (AWS_ACCESS_KEY, AWS_SECRET_ACCESS_KEY,

AWS_SESSION_TOKEN)

- Java System Properties - aws.accessKeyId and aws.secretKey

- Credential profiles file at the default

location (~/.aws/credentials) shared by all AWS SDKs and the AWS CLI

- Instance Profile Credentials - delivered through the Amazon EC2

metadata service

* The implementation assumes that only ONE authentication can be used

per s3-resource at a time

* This patch enforces that each Authentication now declares

`requiresCredentials` to be explicit

Integration tests:

Note that we cannot mock the instance meta data since it uses the ip

169.254.169.254 so we mock the system properties that the client

CredentialsProviderChain will look for.

  1. … 21 more files in changeset.
Address review items for Authentication types

+review REVIEW-5569

  1. … 18 more files in changeset.
fix checkstyle

  1. … 1 more file in changeset.
Normalize authentication package names

+review REVIEW-5569

    • -0
    • +26
    ./DefaultBasicAuthentication.java
    • -0
    • +27
    ./DefaultDigestAuthentication.java
  1. … 43 more files in changeset.