[GRADLE-2335] Provide the ability to implement a custom HTTP authentication scheme for repository access Created: 04/Jun/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Daz DeBoer Assignee: Unassigned
Resolution: Won't Fix Votes: 2


From ZenDesk: What we need to do is to intercept the HTTP request/responses made to the repository. This would let us implement any authentication mechanism that we need plus would give us the ability to send or recieve proprietary headers.

Maven's wagon facilty does this. My only suggestion would be that we would like to have more access to the build context of the request.

Comment by Juraj Martinka [ 26/May/15 ]

Any update on this? Is there any plan to implement this behavior?
Unfortunately, we are not able to run gradle builds in our company because we our using kerberos authentication for our Nexus repository.

Comment by Daz DeBoer [ 27/May/15 ]

We don't have plans to expose the HTTP protocol for repository access. On the other hand, our backing HttpClient instance can be configured to support Kerberos authentication. I guess that would solve that particular use case.

Comment by Henry Tung [ 30/Sep/16 ]

@daz Can you describe in more detail how to configure the backing HttpClient to use Kerberos? And/or are there any code examples available? A way to configure the HttpClient directly would probably be enough to satisfy my use case as well (adding a token header to each request to the repository).

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:19:06 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.