Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <4B675877.60200@die-schneider.net>
Date: Mon, 01 Feb 2010 23:40:55 +0100
From: Christian Schneider <chris@die-schneider.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; de;
 rv:1.9.1.7) Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1
MIME-Version: 1.0
To: users@cxf.apache.org
Subject: Re: Spring Security with CXF JMS Endpoint
References: <27409262.post@talk.nabble.com>
 <201002011516.35372.dkulp@apache.org>
 <b67458761002011347x5c8b4663y852ecb77c8edb114@mail.gmail.com>
 <27412082.post@talk.nabble.com>
In-Reply-To: <27412082.post@talk.nabble.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi John,

some time ago I wrote a really small HTTP2JMSBridge 
(http://www.liquid-reality.de:8080/display/liquid/HTTP2JMSBridge).
It has the ability to create a connection to the jms provider with the 
username/password given to it by using http basic auth.
The bridge even pools the connections.

Having said that the code is probably not production ready but it is 
apache licensed. So I am sure you can tweak it to your needs.

Greetings

Christian

Am 01.02.2010 22:55, schrieb johnpfeifer4:
> I've done some digging... I'm going to need the username and password to
> validate against our spring security authentication provider.
>
> I'm thinking that I could configure the interceptor to look for user/pass in
> JMS Headers or in a single header (in the case of Basic Auth).  I'll have to
> dig around a bit more and let you know what I find.
>
> Thanks,
>
> John
>    

-- 

Christian Schneider
---
http://www.liquid-reality.de