[
https://issues.apache.org/jira/browse/IGNITE-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371355#comment-16371355
]
Vladimir Ozerov commented on IGNITE-7436:
-----------------------------------------
[~tledkov-gridgain]. my comments:
1) {{DiscoveryCustomOnlyForServerMessage}} ->
{{DiscoveryServerOnlyCustomMessage}}
2) Passwords should be persisted w/o persistence (remove on-heap metastore)
3) {{ServerImpl}} - it is not a good idea to unmrashal original custom message
to check whether it should be sent to the client or not. Reasons: a)
performance; b) we do not want to have another code piece requiring
deserialziatio of potentially missing class on the server. It is better to
create another implementation of TcpDiscoveryCustomEventMessage for server-only
messages. Can we do that without breaking protoocl desperately?
> Username/password authentication for thin clients
> -------------------------------------------------
>
> Key: IGNITE-7436
> URL: https://issues.apache.org/jira/browse/IGNITE-7436
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc, odbc, thin client
> Affects Versions: 2.3
> Reporter: Taras Ledkov
> Assignee: Taras Ledkov
> Priority: Major
> Fix For: 2.5
>
>
> This is an umbrella ticket to track all task related to the thin clients
> authentication.
> [Devlist
> discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Username-password-authentication-for-thin-clients-td26058.html]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
