Hi Andrei, good to know – thank you.
So we need to distinguish between auth for 1. thin clients like JDBC clients and 2. thick clients (Java client that wants to join the cluster (as server or client)) I will look at GridSecurityProcessor for item 2 but in the meantime: I saw the CREATE command to create new SQL users on a freshly started cluster. How would you execute that using Java code? Would the app need to start the cluster, then use the Ignite JDBC driver to connect to the (PUBLIC) schema of that cluster, then run the CREATE SQL command and then exit? Kurt From: Andrei Aleksandrov <[email protected]> Sent: Monday, September 16, 2019 12:13 PM To: [email protected] Subject: Re: Authentication External Email: Use caution in opening links or attachments. Hi, I guess that here Ignite has some documentation gap. Advanced security out of the box will work only with thin connections like webconsole, ODBC/JDBC, etc. To get cluster node authentication you should add GridSecurityProcessor implementation: https://apacheignite.readme.io/docs/advanced-security#section-enable-authentication<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheignite.readme.io%2Fdocs%2Fadvanced-security%23section-enable-authentication&data=02%7C01%7Cksemba%40extremenetworks.com%7C596f2dd5794c4f2ac42008d73a8e6e93%7Cfc8c2bf6914d4c1fb35246a9adb87030%7C0%7C0%7C637042255736541107&sdata=JvE0yIHv2EDyVKKfGPZYe7XFe1cR797GnxGkrR8SSeY%3D&reserved=0> I created ticket on documentation: https://issues.apache.org/jira/browse/IGNITE-12170<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FIGNITE-12170&data=02%7C01%7Cksemba%40extremenetworks.com%7C596f2dd5794c4f2ac42008d73a8e6e93%7Cfc8c2bf6914d4c1fb35246a9adb87030%7C0%7C0%7C637042255736551100&sdata=okrAhi7i44OewjWQxYQqUdECIEqpFxBPBA%2F13%2F%2FvMBI%3D&reserved=0> BR, Andrei 9/16/2019 10:43 AM, Kurt Semba пишет: Hi all, I used the web-console to auto-generate some code and then extended the ServerNodeCodeStartup.java class according to the documentation to enable authentication (which requires to enable persistence) like this: public static void main(String[] args) throws Exception { IgniteConfiguration cfg = ServerConfigurationFactory.createConfiguration(); // Ignite persistence configuration. DataStorageConfiguration storageCfg = new DataStorageConfiguration(); // Enabling the persistence. storageCfg.getDefaultDataRegionConfiguration().setPersistenceEnabled(true); // Applying settings. cfg.setDataStorageConfiguration(storageCfg); // Enable authentication cfg.setAuthenticationEnabled(true); Ignite ignite = Ignition.start(cfg); // Activate the cluster. // This is required only if the cluster is still inactive. ignite.cluster().active(true); // Get all server nodes that are already up and running. Collection<ClusterNode> nodes = ignite.cluster().forServers().nodes(); // Set the baseline topology that is represented by these nodes. ignite.cluster().setBaselineTopology(nodes); } But when I run this, the output shows “authentication=off” and I can also connect a client without providing any user+pass… […] [08:57:13] Security status [authentication=off, tls/ssl=off] […] [08:57:16] Ignite node started OK (id=1f668071, instance name=ImportedCluster6) [08:57:16] Topology snapshot [ver=1, locNode=1f668071, servers=1, clients=0, state=INACTIVE, CPUs=4, offheap=2.3GB, heap=2.6GB] [08:57:16] ^-- Baseline [id=0, size=1, online=1, offline=0] [08:57:16] ^-- All baseline nodes are online, will start auto-activation [08:57:16] Ignite node stopped in the middle of checkpoint. Will restore memory state and finish checkpoint on node start. [08:57:16] Both Ignite native persistence and CacheStore are configured for cache 'NsdevicesCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details. Any idea what I’m doing wrong? I will also look into enabling TLS but wanted to start with user+pass auth. Thanks Kurt
