Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAFwzmVA=dnJEY_sLyyD3Ts2fgm6xEubnxWNf2n8FxkNprtKqiQ@mail.gmail.com>
References: 
 <CAFwzmVA=dnJEY_sLyyD3Ts2fgm6xEubnxWNf2n8FxkNprtKqiQ@mail.gmail.com>
Date: Sat, 12 Dec 2015 14:57:07 -0500
Message-ID: 
 <CAHX0R7GYi-Qd-3M_m=kU9ykgeUdQqGEJqFLpo8K5P=7WFfvzQA@mail.gmail.com>
Subject: Re: Introducing gatewayId to SecurityToken in Airavata API
From: Pankaj Saha <psaha4@binghamton.edu>
To: dev <dev@airavata.apache.org>
Content-Type: multipart/alternative; boundary=001a11c1d2064873f60526b8d8c6

--001a11c1d2064873f60526b8d8c6
Content-Type: text/plain; charset=UTF-8

Hi Supun,
Is there any changes required in term of hosted Airavata setup due to this
mandatory field in SecurityToken for 16 branch?

Thanks
Pankaj

On Fri, Dec 11, 2015 at 10:17 PM, Supun Nakandala <supun.nakandala@gmail.com
> wrote:

> Hi devs,
>
> Currently in the Airavata API we use the gatewayId only for some API
> methods like createExperiment, registerApplication etc.. I would like to
> suggest that we move this field to SecurityToken and make it mandatory for
> all API methods. For API methods which requires the gatewayId we can read
> it from there.
>
> By making gatewayId a mandatory field in SecurityToken, in the API it is
> easy to implement access control to the API in a multi tenanted scenario.
>
> Any Concerns?
>
> Thanks
> Supun
>

--001a11c1d2064873f60526b8d8c6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Supun,<div>Is there any changes required in term of hos=
ted Airavata setup due to this mandatory field in SecurityToken for 16 bran=
ch?</div><div><br></div><div>Thanks</div><div>Pankaj</div></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Dec 11, 2015 at 10:=
17 PM, Supun Nakandala <span dir=3D"ltr">&lt;<a href=3D"mailto:supun.nakand=
ala@gmail.com" target=3D"_blank">supun.nakandala@gmail.com</a>&gt;</span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Hi devs,</div=
><div><br></div><div>Currently in the Airavata API we use the gatewayId onl=
y for some API methods like createExperiment, registerApplication etc.. I w=
ould like to suggest that we move this field to SecurityToken and make it m=
andatory for all API methods. For API methods which requires the gatewayId =
we can read it from there.</div><div><br></div><div>By making gatewayId a m=
andatory field in SecurityToken, in the API it is easy to implement access =
control to the API in a multi tenanted scenario.</div><div><br></div><div>A=
ny Concerns?=C2=A0</div><div><br></div><div>Thanks</div><span class=3D"HOEn=
Zb"><font color=3D"#888888"><div>Supun</div>
</font></span></div>
</blockquote></div><br></div>

--001a11c1d2064873f60526b8d8c6--