Mailing-List: contact chemistry-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chemistry-dev@incubator.apache.org
Message-ID: <1577133461.1246376148903.JavaMail.jira@brutus>
Date: Tue, 30 Jun 2009 08:35:48 -0700 (PDT)
From: "Ugo Cei (JIRA)" <jira@apache.org>
To: chemistry-dev@incubator.apache.org
Subject: [jira] Updated: (CMIS-21) HttpClientConnector sets credentials in
 constructor
In-Reply-To: <1646439954.1246376148814.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CMIS-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ugo Cei updated CMIS-21:
------------------------

    Status: Open  (was: Patch Available)

> HttpClientConnector sets credentials in constructor
> ---------------------------------------------------
>
>                 Key: CMIS-21
>                 URL: https://issues.apache.org/jira/browse/CMIS-21
>             Project: Chemistry
>          Issue Type: Bug
>          Components: atompub, client
>            Reporter: Ugo Cei
>            Priority: Critical
>         Attachments: patch.txt
>
>
> The constructor for the HttpClientConnector takes a ContentManager as argument and sets up preemptive authentication using the CredentialsProvider stored in the ContentManager.
> The problem is that, at this point, the CredentialsProvider is null as we haven't yet had a chance to call ContentManager.login, thus the CredentialsProvider will be null. The solution is to differ the setting up of preemptive auth to when ContentManager.login is called.
> The attached patch does exactly this. It's a bit of a quick fix and uses a couple instanceof operations which I don't like much, so you might want to review it and make it better.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.