missing NTLM support for proxy configuraiton

Description

MS ISA is a commonly used proxy/firewall application that may only allow authenticated connections.

The current implementation of UPM supports only limited numbers of attributes. However, it is currently missing support for NTLM:

This attributes are already supported by our application such as Confluence. Other examples of attributes are:

See: http://confluence.atlassian.com/display/DOC/Configure+Web+Proxy+Support+for+Confluence

Related to JSP-77162 on SAC

Environment

1.3.1

Testing Notes

None

Security Policy

None

Activity

Show:
AdrienA
July 1, 2011, 12:36 AM

IT was fixed, but not usable: SAL doesn't support NTLM but uses the same system properties. So setting NTLM properties for PAC would make SAL stop working. We can't deliver it like this.

James Wong
July 5, 2011, 10:30 PM

We don't have the environment to test this so I'm resolving this as "Won't Fix" - we can't officially support this.

Bernard O'Flynn
July 6, 2011, 6:11 AM

Surely someone can pull down a trial version of MS ISA server or one of the other hundreds of NTLM based proxy servers and set this up?
Resolving as Won't Fix because an environment can't be setup seems a bit of a cop out.

DavidD
July 7, 2011, 12:12 AM

Hi Bernard,

First up: nice surname

When it comes to supporting a specific configuration, unfortunately there's a lot more to it than just a one-time download-and-check. We need to:

  • Set it up in our Continuous Integration infrastructure.

  • Configure tests to run for each product.

  • Monitor the builds and fix any breakages. We ran over 65000 builds last month, and someone needs to look at and respond to every red build.

  • Build infrastructure for support engineers to replicate customer issues.

  • Train support engineers to diagnose NTLM authN issues.

All of this takes time and energy. Instead, we've decided to spend that time on work that's applicable to a broader section of our 22000+ commercial customer base. For example, we're spending a lot of time to make it easier to discover useful plugins. We're also investing in stabilising our APIs, so plugins are less likely to break in the future. And we've put a lot of time and energy into making it easier to install and upgrade JIRA and Confluence.

It's our belief that that work is a better investment of our limited resources, as the results will benefit all customers. You'll see these changes start to appear with JIRA 4.4 and continue through the year.

Does that make sense?

Cheers,
Dave.
Integration Product Manager.

Bernard O'Flynn
July 7, 2011, 6:12 AM

Same to you on the surname

Yeh I get that you have limited resources. I'm guessing that we're the not only customers that need NTLM support in UPM? Any windows based corporate will have the issue.

Its just disappointing is all.

Assignee

James Wong

Reporter

BogdanB

Team

None

QA Dev

None

Needs Doc

None

Peer Reviewer

None

Mgr Approver

None

CC

None

Product

None

App Key

None

DC app ready for review?

None

App ID

None

Fix versions

Priority

Critical
Configure