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 <[email protected]> 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
