-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/09/10 17:23, Paul Larson wrote:
>> Other options are (off the top of my head):
>> - - Basic/Digest HTTP authentication. Digest is pretty good (or so
>>
> I think this would fit our needs just fine.
I agree, and for the moment I'd like to pursue
Here's my $0.02 (adjusted for inflation):
On Sat, Sep 4, 2010 at 11:32 AM, Zygmunt Krynicki <
zygmunt.kryni...@linaro.org> wrote:
> I think that for our internal use cases a best option would be launchpad
> integration. We don't mind using launchpad, we already have accounts
> there. We could use
On Sun, 05 Sep 2010 17:25:14 +1200, Michael Hudson
wrote:
> I may be talking out of my behind here, but do you really mean oauth?
> OAuth is more about authorization -- should this request be permitted --
> and the subject of this mail talks about "authentication" -- who is this
> request on beha
First up, let me apologize for the slightly waffly nature of this
email. I'm not an expert in this area, but I hope I know enough to be
of some use...
On Sat, 04 Sep 2010 18:32:30 +0200, Zygmunt Krynicki
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello guys.
>
> I'd like to
On Sat, 04 Sep 2010 18:32:30 +0200, Zygmunt Krynicki
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello guys.
>
> I'd like to ask for your advice in for implementing authentication
> mechanism for the XML-RPC interface to the dashboard. I believe this
> problem has two aspects:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello guys.
I'd like to ask for your advice in for implementing authentication
mechanism for the XML-RPC interface to the dashboard. I believe this
problem has two aspects: user needs and client program needs. I was
about to implement HTTP Digest auth
