abon" <lpa...@redhat.com>, "Kanagaraj Mayilsamy"
<kmayi...@redhat.com>, "Gluster Devel" <gluster-devel@gluster.org>, "Kaushal
Madappa" <kmada...@redhat.com>
Sent: Thursday, March 3, 2016 11:04:17 PM
Subject: Re: [Gluster-devel] REST API
regards
Aravinda
On 03/03/2016 05:58 PM, Kaushal M wrote:
On Thu, Mar 3, 2016 at 2:39 PM, Aravinda wrote:
Thanks.
We can use Shared secret if https requirement can be completely
avoided. I am not sure how to use same SSL certificates in all the
nodes of the
On Thu, Mar 3, 2016 at 2:39 PM, Aravinda wrote:
> Thanks.
>
> We can use Shared secret if https requirement can be completely
> avoided. I am not sure how to use same SSL certificates in all the
> nodes of the Cluster.(REST API server patch set 2 was written based on
> shared
Thanks.
We can use Shared secret if https requirement can be completely
avoided. I am not sure how to use same SSL certificates in all the
nodes of the Cluster.(REST API server patch set 2 was written based on
shared secret method based on custom HMAC signing
Hi Aravinda,
Very good summary. I would like to rephrase a few parts.
On the shared token approach, the disadvantage is that the server will be more
complicated (not *really* complicated, just more than the shared token),
because it would need a login mechanism. Server would have to both
-Atin
Sent from one plus one
On 02-Mar-2016 12:23 pm, "Aravinda" wrote:
>
> Hi,
>
> For Gluster REST project we are planning to use JSON Web Token for
> authentication. There are two approaches to use JWT, please help us to
> evaluate between these two options.
>
>