Re: Unable to join using thick client when authentication is enabled

Hi, The bug has been fixed. The fix will be in version 2.12. пн, 22 нояб. 2021 г. в 15:26, Shishkov Ilya : > Hi, > I created a ticket about this problem: > https://issues.apache.org/jira/browse/IGNITE-15969 > > пт, 19 нояб. 2021 г. в 22:46, Shishkov Ilya : > >> Hi, >> I've reproduced it for 2.11.

Re: Unable to join using thick client when authentication is enabled

Hi, I created a ticket about this problem: https://issues.apache.org/jira/browse/IGNITE-15969 пт, 19 нояб. 2021 г. в 22:46, Shishkov Ilya : > Hi, > I've reproduced it for 2.11. In case of turned on authentication, thick > clients won't connect until you enable persistence for them. Because thick

Re: Unable to join using thick client when authentication is enabled

Hi, I've reproduced it for 2.11. In case of turned on authentication, thick clients won't connect until you enable persistence for them. Because thick clients have no persistence, you can use it like a workaround. Certainly, it looks like a bug. пт, 19 нояб. 2021 г. в 16:42, Ganguly Gundeboina :

Re: Unable to join using thick client when authentication is enabled

Hi Stephen, Same already tried, but it's giving below error even though we have enabled persistence. # [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT [18:03:39] Message qu

Re: Unable to join using thick client when authentication is enabled

Thick clients don’t need to authenticate, but they do need to have the same authentication settings as the server nodes, i.e., set IgniteConfiguration#setAuthenticationEnabled(true). > On 19 Nov 2021, at 11:28, Ganguly Gundeboina wrote: > > Hi Pavel, > > Yes, we have enabled authentication on

Re: Unable to join using thick client when authentication is enabled

Hi Pavel, Yes, we have enabled authentication on server nodes only. We could provide user credentials for thin clients, so thin clients are able to connect to the cluster after setting username and password at client side. But not able to set user credentials for thik clients, So we have to disa

Re: Unable to join using thick client when authentication is enabled

Hi Gangaiah, Before 2.11, there was no requirement to have an equal security processor on all nodes. It was added as part of [1]. Overall, I think it is a good idea to have security on all nodes configured in the same way. Do you have it enabled only on server nodes? [1] https://issues.apache.or

RE: Unable to join using thick client when authentication is enabled

Gangaiah, this exception means that authentication is disabled on the thick client and enabled on the cluster it was trying to connect to. Enable authentication on the thick client and the problem should be solved. -- Mikhail On 2021/11/17 17:56:13 Ganguly Gundeboina wrote: > Hi Igniters, >

Re: Unable to join using thick client when authentication is enabled

Hi Andrei, Thanks for your reply, here is the full log. "C:\Program Files\Java\jdk1.8.0_241\bin\java.exe" -Dvisualvm.id=14727407530300 -DMIGRATION_CONFIG_PATH=C:\Users\scott\AzureRepos\Ignite-Utilities\SourceCode\ignite-util\src\main\resources\migration-config.properties "-javaagent:C:\Program Fi

Re: Unable to join using thick client when authentication is enabled

Hello, Could you please provide a full exception for this node? If you can provide complete logs, it will be even better. I see locCls=null, but as I can see from the code it should be locCls=processor.getClass().getName(). I'm not sure how it can be null. Regards, Andrei 11/17/2021 8:56 P

Unable to join using thick client when authentication is enabled

Hi Igniters, We recently started using Ignite version 2.11.0 (native persistence enabled) with authentication enabled. When am trying to connect to cluster using thick client, getting error as below. This was not there with earlier version. I have checked https://ignite.apache.org/docs/latest/s