This map is something like user object from `SecurityCredentials`. Sometimes login and password are not enough for security checks. For example, we can send security certificate and validate it inside authenticator.
ср, 22 янв. 2020 г., 17:16 Igor Sapego <isap...@apache.org>: > Hi Dmitrii, > > Can you please explain your use case? > I'm not sure I'm getting what is the motivation of this change. > > Best Regards, > Igor > > > On Wed, Jan 22, 2020 at 5:11 PM Pavel Tupitsyn <ptupit...@apache.org> > wrote: > > > Hi Dmitrii, > > > > Honestly, I could not grasp the problem, can you explain it in more > detail? > > What do we solve by adding a map with arbitrary stuff to the client > > protocol handshake? > > > > On Wed, Jan 22, 2020 at 5:02 PM Dmitrii Ryabov <somefire...@gmail.com> > > wrote: > > > > > Hello, Igniters! > > > > > > I want to add the possibility of sending user defined attributes from > > thin > > > clients. And check them inside custom authenticator during handshake > [1]. > > > > > > There is an issue in hardcoded binary writer for JDBC and > `IgniteClient`. > > > This writer searches for a classes in the JDK and > > > META-INF/classnames.properties, and tries to sync notdeclared classes > > with > > > cluster. But fails because current classloading uses discovery. > > > > > > I'd like to keep this writer and allow only primitive types and > `String` > > > for user attributes to prevent unexpected fails. I think it is better > > than > > > changing writer to one with heavy classloading. > > > > > > Is it ok to restrict thin attributes to primitives and 'String'? > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12049 > > > > > >
