Understandable although in our case we don't use the scheme to
actually talk with Amazon. We've implemented the scheme in both client
and server form as our sole means of auth since it is easy, stateless,
very secure and doesn't require SSL overhead.
Just food for thouught. I'll create a JIRA ticket.
Cheers,
Jean-Philippe
On Mar 13, 2010, at 1:40 AM, Oleg Kalnichevski <[email protected]> wrote:
On Fri, 2010-03-12 at 13:25 -0800, Jean-Philippe Steinmetz wrote:
The implementation only depends on commons-codec and httpclient.
That's it!
=)
Jean-Philippe
This certainly makes things easier.
I am not sure a vendor specific auth scheme, which none of the actual
project committers is able to support, should belong to the HttpClient
proper, but we can certainly accept your code into the contrib (source
only) package. If that is okay with you please feel free to go ahead
and
create a JIRA ticket for your contribution and attach the source
code to
it.
Cheers
Oleg
On Fri, Mar 12, 2010 at 12:12 PM, Oleg Kalnichevski
<[email protected]>wrote:
Jean-Philippe Steinmetz wrote:
Hi Oleg,
Thank you for your response. I realized my issue last night with
my scheme
not implementing challenge. I've been developing an
implementation of
Amazon
S3 authentication which requires no challenge. I didn't realize
that there
was a difference until I started reading more carefully about
preemptive
auth schemes. By setting up my scheme as preemptive I was able to
get it
to
work.
On a side note if the project is interested in having an Amazon
S3 auth
implementation I'd be happy to submit it.
Hi Jean-Philippe
Does Amazon S3 auth implementation depend on any third party
libraries, and
if so, what license they are covered by?
Oleg
---
------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
