Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <1470919976127-6976.post@n6.nabble.com>
References: <1470664526128-6853.post@n6.nabble.com> <CADez4_UsQvtVfTXYNNKpL0opC3-xCPMQk800ca1RZY19sjkP+g@mail.gmail.com>
 <1470691112982-6860.post@n6.nabble.com> <1470919976127-6976.post@n6.nabble.com>
From: Vladislav Pyatkov <vldpyatkov@gmail.com>
Date: Thu, 11 Aug 2016 16:54:51 +0300
Message-ID: <CADez4_Ux0ZM79-6MgS+ob9sEEFJCpdgVGxZdtZoDOFWD4LdVDQ@mail.gmail.com>
Subject: Re: Node authentication using security credentials
To: user@ignite.apache.org
Content-Type: multipart/alternative; boundary=94eb2c064ac02de58b0539cc1c16
archived-at: Thu, 11 Aug 2016 13:54:58 -0000

--94eb2c064ac02de58b0539cc1c16
Content-Type: text/plain; charset=UTF-8

Hi,

Authentication process protects access to grid in first, but authorization
allow to determine list of authorized permissions.
In other word you can have some clients with difference rights. Any user
can have or have not permission to grid functionality. Description of the
permission you can see in the enum
org.apache.ignite.plugin.security.SecurityPermission.

On Thu, Aug 11, 2016 at 3:52 PM, pragmaticbigdata <amits.84@gmail.com>
wrote:

> When you mention "Ignite has all the hooks in the code" I think you are
> referring the the plugin support that ignite provides and the classes under
> the package "org.apache.ignite.plugin.security".
>
> What could be the reasons of having a security layer given that ignite
> would
> be deployed on a private aws network (VPC)? I do not foresee a need of
> having client authentication but just wanted to know your thoughts.
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Node-authentication-using-security-
> credentials-tp6853p6976.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>


-- 
Vladislav Pyatkov

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

<div dir=3D"ltr"><div>Hi,</div><div><br></div><div>Authentication process p=
rotects access to grid in first, but authorization allow to determine list =
of authorized permissions.</div><div>In other word you can have some client=
s with difference rights. Any user can have or have not permission to grid =
functionality. Description of the permission you can see in the enum org.ap=
ache.ignite.plugin.security.SecurityPermission.</div></div><div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote">On Thu, Aug 11, 2016 at 3:52 PM, =
pragmaticbigdata <span dir=3D"ltr">&lt;<a href=3D"mailto:amits.84@gmail.com=
" target=3D"_blank">amits.84@gmail.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">When you mention &quot;Ignite has all the hooks in the =
code&quot; I think you are<br>
referring the the plugin support that ignite provides and the classes under=
<br>
the package &quot;org.apache.ignite.plugin.<wbr>security&quot;.<br>
<br>
What could be the reasons of having a security layer given that ignite woul=
d<br>
be deployed on a private aws network (VPC)? I do not foresee a need of<br>
having client authentication but just wanted to know your thoughts.<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://apache-ignite-users.70518.x=
6.nabble.com/Node-authentication-using-security-credentials-tp6853p6976.htm=
l" rel=3D"noreferrer" target=3D"_blank">http://apache-ignite-users.<wbr>705=
18.x6.nabble.com/Node-<wbr>authentication-using-security-<wbr>credentials-t=
p6853p6976.html</a><br>
<div class=3D"HOEnZb"><div class=3D"h5">Sent from the Apache Ignite Users m=
ailing list archive at Nabble.com.<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature">Vladislav=
 Pyatkov</div>
</div>

--94eb2c064ac02de58b0539cc1c16--