You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Igor Sapego (Jira)" <ji...@apache.org> on 2022/08/09 03:46:00 UTC

[jira] [Commented] (IGNITE-17494) Python thin: Fix client authentication/TLS defaults

    [ https://issues.apache.org/jira/browse/IGNITE-17494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17577120#comment-17577120 ] 

Igor Sapego commented on IGNITE-17494:
--------------------------------------

Tests passed:
https://ci.ignite.apache.org/buildConfiguration/IgniteThinClients_Tests_ThinClientPythonAllPythons/6719485
https://ci.ignite.apache.org/buildConfiguration/IgniteThinClients_Tests_ThinClientPython/6719483

> Python thin: Fix client authentication/TLS defaults
> ---------------------------------------------------
>
>                 Key: IGNITE-17494
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17494
>             Project: Ignite
>          Issue Type: New Feature
>          Components: python, thin client
>    Affects Versions: python-0.5.2
>            Reporter: Igor Sapego
>            Assignee: Igor Sapego
>            Priority: Major
>             Fix For: python-0.6.0
>
>
> If you specify a username/password to the Python thin-client it automatically switches use_ssl to True. The logic here is understandable but it’s confusing when two orthogonal settings are related like this. Some users mentioned it too.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)