Hi,
You are absolutely right.
In case you use thin JDBC driver (recommended):
1. You have to define SSLContext factory for client connector for Ignite
node [1]
2. And setup SSL socket factory for Ignite thin JDBC driver [2]
If you are going to use JDBCv2 driver please keep in mind that the
JDBCv2 driver starts
the Ignite client node to connect to Ignite cluster and read the
documentation [3]
[1]
org.apache.ignite.configuration.ClientConnectorConfiguration#setSslContextFactory
(https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ClientConnectorConfiguration.html)
[2] See `sslFactory` property:
https://apacheignite-sql.readme.io/docs/jdbc-driver#jdbc-thin-driver
[3] https://apacheignite-sql.readme.io/docs/jdbc-client-driver
On 28.08.2018 12:39, wt wrote:
i have finally managed to get a plugin working for a white list on ignite
2.6. I am now going to start working on an authorization for users
connecting to the cluster.
How can i get clients pass through a kerberos ticket to the cluster? I think
i need to override the authorization context class but that would mean that
i need to do it both on the server and the clients for odbc\jdbc etc.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
--
Taras Ledkov
Mail-To: [email protected]
