Pavel,
At the moment it is only supported by thin clients. In future we will
expand this mechanism to normal nodes as well.
On Tue, Mar 27, 2018 at 10:55 AM, Pavel Tupitsyn
wrote:
> IGNITE-8034 done, I have added configuration flag.
>
> However, I still have concerns about property naming:
> Is
Hi Pavel,
.NET core tests are passing now.
Let me sincerely thank you for helping the community in keeping TC to be
green.
Best Regards,
Dmitriy Pavlov
вт, 27 мар. 2018 г. в 10:55, Pavel Tupitsyn :
> IGNITE-8034 done, I have added configuration flag.
>
> However, I still have concerns about pr
IGNITE-8034 done, I have added configuration flag.
However, I still have concerns about property naming:
Is this authentication going to be used for thin clients only, or for
classic client and server nodes as well?
On Tue, Mar 27, 2018 at 9:50 AM, Dmitry Pavlov
wrote:
> Hi Folks,
>
> Test is s
Hi Folks,
Test is still failing on TC.
https://ci.ignite.apache.org/viewLog.html?buildId=1160178&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_IgnitePlatformNetCoreLinux
I suggest to mute it until fix is ready.Test is running in Basic Run All
subsets, so each commit will genereate TC failure
Taras,
Please document the authentication part on a 2.5 version of the binary
protocol page on readme.io. We need to share it with the guys who are
developing Node.JS client right now.
--
Denis
On Mon, Mar 26, 2018 at 2:55 AM, Taras Ledkov wrote:
> I had implement user credential store accordi
I had implement user credential store according with the previous
discussion about user authentication.
Now JDBC thin, and ODBC support user authentication. We haven't
implemented it for all thin client because protocols are not similar.
I see two ways to implement authentication for thin cli
Taras,
Could you please chime in?
On Mon, Mar 26, 2018 at 9:56 AM, Pavel Tupitsyn
wrote:
> I've started this task, and the property name combined with lack of
> javadoc seems confusing and misleading:
>
> * Turns out this authentication is only for thin clients
> * Not clear how to configure an
I've started this task, and the property name combined with lack of javadoc
seems confusing and misleading:
* Turns out this authentication is only for thin clients
* Not clear how to configure and use it, even after digging through Jira
and devlist
How do I write test to ensure it works?
Thanks
Thanks, got it, will do.
On Fri, Mar 23, 2018 at 4:36 PM, Dmitry Pavlov
wrote:
> Hi Pavel,
>
> Related ticket is https://issues.apache.org/jira/browse/IGNITE-7436
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 23 мар. 2018 г. в 16:24, Pavel Tupitsyn :
>
> > Please provide description in IGNITE-8034 and
Hi Pavel,
Related ticket is https://issues.apache.org/jira/browse/IGNITE-7436
Sincerely,
Dmitriy Pavlov
пт, 23 мар. 2018 г. в 16:24, Pavel Tupitsyn :
> Please provide description in IGNITE-8034 and link Java-side ticket there.
>
> On Fri, Mar 23, 2018 at 4:23 PM, Pavel Tupitsyn
> wrote:
>
> >
Hi Pavel,
I added the link to original ticket.
On Fri, Mar 23, 2018 at 4:24 PM, Pavel Tupitsyn
wrote:
> Please provide description in IGNITE-8034 and link Java-side ticket there.
>
> On Fri, Mar 23, 2018 at 4:23 PM, Pavel Tupitsyn
> wrote:
>
>> Hi Vladimir,
>>
>> Can you provide more details?
Please provide description in IGNITE-8034 and link Java-side ticket there.
On Fri, Mar 23, 2018 at 4:23 PM, Pavel Tupitsyn
wrote:
> Hi Vladimir,
>
> Can you provide more details?
> * What does it do?
> * Do we need to only propagate the flag to .NET or do anything else?
> * Related ticket?
>
> T
Hi Vladimir,
Can you provide more details?
* What does it do?
* Do we need to only propagate the flag to .NET or do anything else?
* Related ticket?
Thanks,
Pavel
On Fri, Mar 23, 2018 at 2:25 PM, Vladimir Ozerov
wrote:
> Pavel,
>
> We introduced new flag IgniteConfiguration.authenticationEnabl
Pavel,
We introduced new flag IgniteConfiguration.authenticationEnabled recently.
Would you mind adding it to IgniteConfigutation.cs [1]?
Vladimir.
[1] https://issues.apache.org/jira/browse/IGNITE-8034
14 matches
Mail list logo
