Oh, wait, I am being _really_really_ stupid... You're talking about the
client side...
I thought you were talking about the server... I thought something was
amiss with my perceptions, but didn't realize it would be that basic--I saw
the word "Filter" and was thinking of Servlet Filters, which happened to be
a discussion I was having recently for the very purpose of adding some
security related aspects to something. Sigh, I'll squirm back under my rock
now; sorry for wasting time and bandwidth.
---------- Forwarded message ----------
> From: Stefan Katerkamp <stefan_at_katerkamp.de>
> To: users_at_jersey.java.net
> Cc:
> Date: Sun, 07 Jul 2013 21:48:19 +0200
> Subject: [Jersey] Re: Digest for list users_at_jersey.java.net
> Hi Simon,
>
> well, dunno. Maybe I failed to find some already existing Jersey 2
> HttpDigestAuthFilter. At least I could not find it. Please advise.
>
> My understanding so far: For 1.x there is HTTPDigestAuthFilter. Jersey 1
> used a single handler method for the filter, and Jersey 2 uses 2 different
> filters with 2 methods for FromWire and ToWire.
>
> I simply took HTTPDigestAuthFilter and rewrote it for Jersey 2.0. This
> allowed me to use Jersey 2, SSL plus Digest Authentication on the client
> side, and it also works inside a Glassfish 4 application. I just focused on
> getting my problem solved. (BTW If I was right and there really is no such
> filter for Jersey 2 yet, and if this filter has a chance to get accepted,
> I'd be willing to go through these paperworks and sign the Oracle
> contributor agreement.)
>
> Cheers
> Stefan
>
>
> Am 07.07.2013 16:40, schrieb Simon Roberts:
>
> So, this tells me that I've misunderstood something. Java EE, and with it
> Glassfish, support digest authentication, and that transfers to JAX-RS
> through the regular security mechanisms, and that has always appeared to
> me, in theory at least, to be enough.
>
> So, what am I missing? What does the provided mechanism not get you that
> you need to do this?
>
> TIA!
>
> From: Stefan Katerkamp <stefan_at_katerkamp.de>
>> To: users_at_jersey.java.net
>> Cc:
>> Date: Sat, 06 Jul 2013 01:20:39 +0200
>> Subject: [Jersey] Jersey 2 Client Digest Auth Filter available
>> Hi,
>>
>> just to let you know:
>>
>> I needed Http client Digest authentication for my Glassfish 4 app. I
>> could not find any auth filter for it, so I wrote my own.
>>
>> I works fine for me, it may need further testing. Feel free to try
>> evaluate it and possibly integrate it with the distribution.
>>
>> Code can be found here: http://katerkamp.de/software/jersey/
>>
>> BR
>> Stefan Katerkamp
>>
>> End of digest for list users_at_jersey.java.net - Sat, 06 Jul 2013
>>
>>
>
>
>
> ---------- Forwarded message ----------
> From: buko <buko_at_chiubarobot.com>
> To: users_at_jersey.java.net
> Cc:
> Date: Sun, 7 Jul 2013 19:54:28 -0400
> Subject: [Jersey] Re: Jersey 2 Client Digest Auth Filter available
> Stefan,
>
> Thanks. This is pretty cool. I'm surprised there aren't more examples
> about authentication and Jersey. Besides [1] and the short section on
> client authentication I couldn't find much else. This is a pretty common
> use case so there should probably be better docs.
>
> [1]
> https://github.com/jersey/jersey/blob/master/examples/https-clientserver-grizzly/src/main/java/org/glassfish/jersey/examples/httpsclientservergrizzly/SecurityFilter.java
>
>
> On Fri, Jul 5, 2013 at 7:20 PM, Stefan Katerkamp <stefan_at_katerkamp.de>wrote:
>
>> Hi,
>>
>> just to let you know:
>>
>> I needed Http client Digest authentication for my Glassfish 4 app. I
>> could not find any auth filter for it, so I wrote my own.
>>
>> I works fine for me, it may need further testing. Feel free to try
>> evaluate it and possibly integrate it with the distribution.
>>
>> Code can be found here: http://katerkamp.de/software/**jersey/<http://katerkamp.de/software/jersey/>
>>
>> BR
>> Stefan Katerkamp
>>
>
>
> End of digest for list users_at_jersey.java.net - Mon, 08 Jul 2013
>
>
--
Simon Roberts
(303) 249 3613