Hi Taras
I am slightly confused. You are mentioning sslcontext and looking at those
related classes it doesn't appear to offer authentication and authorization.
Here is where i currently am with this project.
I have a white list plugin that i will apply to server nodes when they join.
I have yet to implement a check to see if the node is a client or a server
so my assumption at this point is all nodes (clients and servers) will be
validated against the white list.
The next step is to add user authentication (not the ignite built-in
version) and also authorization to lock down what users can access and do.
my current additional classes are:
WhiteListPluginConfiguration implements PluginConfiguration
WhiteListPluginProvider implements
PluginProvider<WhiteListPluginConfiguration>
WhiteListSecurityProcessor
implements DiscoverySpiNodeAuthenticator,
GridSecurityProcessor,
IgnitePlugin
Can you please advise on my next steps such as:
1) what classes i need to override and implement for authentication and
authorization
2) do i need a new plugin or can i extend the one i have written
3) once i have implemented the new classes, where to i override to call into
them
4) do i need to change the code in the odbc and jdbc code base to include my
authentication and authorization
My goal here is to be able to
1) prevent a vanilla client from connecting without implementing my security
2) enforce odbc and jdbc and java\.net clients authentication and
authorization
I really appreciate any guidance here as there is no documentation to
support doing this.
Thanks
Wayne
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
