[
https://issues.apache.org/jira/browse/IGNITE-21064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806890#comment-17806890
]
Pavel Tupitsyn commented on IGNITE-21064:
-----------------------------------------
The initial idea was exactly as you say: server and client authenticators
should match. I'm not sure what we are trying to solve here.
> Refactor authentication naming and enum in Thin Client for clarity
> ------------------------------------------------------------------
>
> Key: IGNITE-21064
> URL: https://issues.apache.org/jira/browse/IGNITE-21064
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Reporter: Ivan Gagarkin
> Assignee: Ivan Gagarkin
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, the Thin Client utilizes
> {{org.apache.ignite.security.AuthenticationType}} to specify the
> authentication method during the handshake process. This approach can be
> confusing due to its interaction with the type of authentication defined in
> the configuration. To resolve this, we propose creating a separate
> enumeration specifically for the client. Additionally, the 'BASIC'
> authentication type should be renamed to 'PASSWORD' for clearer understanding.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
