The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:

Feature #16923

Add support for proxy user name and passwords for 'puppet module' tool

Added by Nick Chappell over 3 years ago. Updated over 2 years ago.

Status:UnreviewedStart date:10/10/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-Spent time:-
Target version:-
Keywords:newfeature customer Affected URL:https://support.puppetlabs.com/tickets/1607
Branch:https://github.com/kbarber/puppet/tree/ticket/master/proxy_auth

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket is now tracked at: https://tickets.puppetlabs.com/browse/FORGE-87


Description

This came up in a commercial support ticket. The user has a proxy server that uses authentication and was not able to use the ‘puppet module’ command to search for or install modules from the Puppet Forge. They kept getting HTTP407 errors saying that authentication with the proxy server was required first. The problem lies in /opt/puppet/lib/site_ruby/1.8/puppet/forge/repository.rb. The methods that extract pieces from the URI object the Net:HTTP library uses only extract a proxy hostname and port, not the proxy username and password.

Ken Barber wrote a quick fix, the commit for which can be found here:

https://github.com/kbarber/puppet/commit/38bdd90194c92dba55327c59e200f6c85c952e5c


Related issues

Related to Puppet Forge - Bug #15453: Puppet Module Tool should respect http proxies Needs More Information 07/10/2012

History

#1 Updated by Nick Chappell over 3 years ago

Another issue cropped up where searching the forge worked but downloading modules did not. Ken Barber wrote a fix for this, the commit for which is here:

https://github.com/kbarber/puppet/commit/a11fd97507009563d9b523da221988406247be77

#2 Updated by Ryan Coleman over 3 years ago

  • Project changed from Puppet to Puppet Forge
  • Category deleted (newfeature)
  • Support Urls deleted (https://support.puppetlabs.com/tickets/1607 https://support.puppetlabs.com/tickets/1520)

Moving this to the Forge project for better visibility for the people that maintain this code. Paste module tool tickets have already been moved over.

#3 Updated by Ryan Coleman over 3 years ago

  • Keywords set to newfeature
  • Affected URL set to https://support.puppetlabs.com/tickets/1607 https://support.puppetlabs.com/tickets/1520

Ugh. Lost some metadata in the move. Putting it back some how.

#4 Updated by Ryan Coleman over 3 years ago

  • Affected URL changed from https://support.puppetlabs.com/tickets/1607 https://support.puppetlabs.com/tickets/1520 to https://support.puppetlabs.com/tickets/1607

#5 Updated by Ken Barber over 3 years ago

  • Branch set to https://github.com/kbarber/puppet/tree/ticket/master/proxy_auth

The work for these fixes live in this branch for now:

https://github.com/kbarber/puppet/tree/ticket/master/proxy_auth

#6 Updated by Ryan Coleman over 3 years ago

Ken Barber wrote:

The work for these fixes live in this branch for now:

https://github.com/kbarber/puppet/tree/ticket/master/proxy_auth

Awesome.

Does this mean it’s on a path for release in Puppet or that it’s just out there for experimentation?

#7 Updated by Ryan Coleman about 3 years ago

  • Assignee set to Ken Barber
  • Support Urls deleted (https://support.puppetlabs.com/tickets/1607 https://support.puppetlabs.com/tickets/1520)

Hi Ken, Did this ever make it into a pull against core? If not, what’s left to be done? I’d like to get it rolling again.

#8 Updated by Ryan Coleman about 3 years ago

  • Support Urls deleted (https://support.puppetlabs.com/tickets/1607 https://support.puppetlabs.com/tickets/1520)

I didn’t mean to delete the support urls. Not sure what happened there.

https://support.puppetlabs.com/tickets/1607 https://support.puppetlabs.com/tickets/1520

#9 Updated by Ken Barber about 3 years ago

  • Assignee deleted (Ken Barber)
  • Support Urls deleted (https://support.puppetlabs.com/tickets/1607 https://support.puppetlabs.com/tickets/1520)

Hi Ken, Did this ever make it into a pull against core? If not, what’s left to be done? I’d like to get it rolling again.

Needs tests by the looks of it.

#10 Updated by Charlie Sharpsteen about 3 years ago

  • Keywords changed from newfeature to newfeature customer

#12 Updated by Felix Frank over 2 years ago

  • Support Urls deleted (https://support.puppetlabs.com/tickets/1607 https://support.puppetlabs.com/tickets/1520)

This seems related to #8281, not sure if it’s actually a duplicate.

#13 Updated by Spencer Seebald over 2 years ago

We just had a presales ticket come in with this exact issue:

http://projects.puppetlabs.com/issues/23334

#14 Updated by Anonymous over 2 years ago

Redmine Issue #16923 has been migrated to JIRA:

https://tickets.puppetlabs.com/browse/FORGE-87

Also available in: Atom PDF