[
https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031531#comment-17031531
]
Alexey Scherbakov commented on IGNITE-12049:
--------------------------------------------
[~SomeFire]
1. The change is badly documented. At least we should add a description of the
property here [1]
Please create a documentation ticket.
The javadoc should be more descriptive both for JDBC attrs factory and thin
clients setter.
2. Current approach seems fragile to me because custom authenticator requires
internal API usage and a subject to broke in next releases. It has little value
for community right now. For example, user attributes cannot be used for JDBC
driver without custom authenticator.
Shouldn't we extend build-in Ignite security to support this feature [2] ?
[~ptupitsyn] [~isapego] What steps are need to be done for implementing
support for user attributes for other language clients ?
[1] https://apacheignite.readme.io/docs/advanced-security
[2]
org.apache.ignite.internal.processors.authentication.IgniteAuthenticationProcessor
> Add user attributes to thin clients
> -----------------------------------
>
> Key: IGNITE-12049
> URL: https://issues.apache.org/jira/browse/IGNITE-12049
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ryabov Dmitrii
> Assignee: Ryabov Dmitrii
> Priority: Minor
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Add user attributes to thin clients (like node attributes for server nodes).
> Make sure that custom authenticators can use these attributes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
