1. Thick client/server nodes use a different communication mechanism than Thin client nodes, and network ports are different. Security mechanism is also different.
E.g. you can have a cluster of server nodes running in a controlled environment, with only 10800 port open to the outside. This way only Thin Client nodes can connect from outside, and server-to-server connections do not need authentication. 2. Ignite does not provide ready to use server-to-server auth out of the box (neither Java nor .NET), some third party vendors provide this via plugins. If you have to stick with Ignite, you'll have to write a plugin, part of which has to be in Java. See Ignite.NET plugin system: https://apacheignite-net.readme.io/docs/plugins On Thu, Oct 10, 2019 at 2:07 AM alokyadav12 <[email protected]> wrote: > We are new to Ignite.Net and trying to implement few security feature > before > deciding final implementation in product. > > We had implemented authentication on Ignite Server and when connecting Thin > client it user user id and password and working as expected. > We had noticed that if we spun off another Node then it connects > automatically to running node and doesnt need username and password. > > Question 1 : Does thick client and node does not authenticate when > connecting nodes? > > Question 2 : Found an article to create custome plugin and authenticate > http://smartkey.co.uk/development/securing-an-apache-ignite-cluster/. This > article focused on Java implementation, but we are using Ignite.Net and > didnt find the DiscoverySpiNodeAuthenticator, GridSecurityProcessor > Interfaces to create a plugin. Are these classes available to use in > Ignite.Net? Is there any other alternate available. > > Is there any other way we can authenticate thick client and nodes when > connecting, as we need to secure nodes so only authenticated nodes and > Thick > client can connect. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
