Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sat, 19 Jan 2013 11:08:13 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12537532.1325865070853.163678.1358593693041@arcas>
In-Reply-To: <JIRA.12537532.1325865070853@arcas>
References: <JIRA.12537532.1325865070853@arcas>
Subject: [jira] [Updated] (CAMEL-4869) camel-ahc - Provide easier realm
 configuration possibility
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen updated CAMEL-4869:
-------------------------------

    Summary: camel-ahc - Provide easier realm configuration possibility  (was: Provide easier realm configuration possibility)
    
> camel-ahc - Provide easier realm configuration possibility
> ----------------------------------------------------------
>
>                 Key: CAMEL-4869
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4869
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-ahc
>    Affects Versions: 2.9.0
>         Environment: N/A
>            Reporter: David J. M. Karlsen
>              Labels: ahc, configuration, realm
>             Fix For: 2.11.0
>
>
> It would be nice if the authentication realm object could be configured in the same easy way as the rest of the clientConfig.
> Something like:
> {noformat}
> clientConfig.realm.type=Digest&clientConfig.realm.user=someUser&clientConfig.realm.password=somePass&clientConfig.realm.preemtive=true
> {noformat}
> etc
> Today there is really no option other than using the AHC RealmBuilder directly (which is more cumbersome as the actual values are externalized - and thus plumbing is needed to read these, build a realm, and set it on the component.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira