Hello! If you really need authentication of nodes, you can add SSL configuration with certificate checking.
This means that any rogue node will not be able to join since it does not have proper certificate. This is also much more secure than passwords. Make sure to add SSL to all ports, such as connectors, ODBC, etc. Regards, -- Ilya Kasnacheev чт, 10 окт. 2019 г. в 02:07, alokyadav12 <alokyada...@gmail.com>: > 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/ >
