Disabling ODBC/thin JDBC/thin .NET connectivity

[Igor Sapego-2]

Hi, Igniters,

In current approach, ODBC, thin JDBC and thin .NET client all connect
to the grid using ClientListenerProcessor, which listen on a single port.

The problem is that there is currently no way to disable only one client.
For example, currently you can't disallow thin JDBC driver connectivity
alone, you can only disable the whole ClientListenerProcessor, which is
going to disable ODBC and thin .NET clients as well.

I believe, we should add options to disable/enable every single client,
supported by the ClientListenerProcessor separately. Maybe we should
add such options to the SqlConnectorConfiguration.

What do you guys think?

Best Regards,
Igor

[Pavel Tupitsyn]

Yes, I think it would make sense to add enableJdbc, enableOdbc,
enableThinClients
properties to ClientConnectorConfiguration (which replaces
SqlConnectorConfiguration).

This way users will also have better understanding of the
ClientConnectorConfiguration purpose.

Pavel

On Wed, Sep 20, 2017 at 1:12 PM, Igor Sapego <[hidden email]> wrote:

> Hi, Igniters,
>
> In current approach, ODBC, thin JDBC and thin .NET client all connect
> to the grid using ClientListenerProcessor, which listen on a single port.
>
> The problem is that there is currently no way to disable only one client.
> For example, currently you can't disallow thin JDBC driver connectivity
> alone, you can only disable the whole ClientListenerProcessor, which is
> going to disable ODBC and thin .NET clients as well.
>
> I believe, we should add options to disable/enable every single client,
> supported by the ClientListenerProcessor separately. Maybe we should
> add such options to the SqlConnectorConfiguration.
>
> What do you guys think?
>
> Best Regards,
> Igor
>

[Vladimir Ozerov]

Agree. Do we have a ticket for this?

On Wed, Sep 20, 2017 at 1:27 PM, Pavel Tupitsyn <[hidden email]>
wrote:

> Yes, I think it would make sense to add enableJdbc, enableOdbc,
> enableThinClients
> properties to ClientConnectorConfiguration (which replaces
> SqlConnectorConfiguration).
>
> This way users will also have better understanding of the
> ClientConnectorConfiguration purpose.
>
> Pavel
>
> On Wed, Sep 20, 2017 at 1:12 PM, Igor Sapego <[hidden email]> wrote:
>
> > Hi, Igniters,
> >
> > In current approach, ODBC, thin JDBC and thin .NET client all connect
> > to the grid using ClientListenerProcessor, which listen on a single port.
> >
> > The problem is that there is currently no way to disable only one client.
> > For example, currently you can't disallow thin JDBC driver connectivity
> > alone, you can only disable the whole ClientListenerProcessor, which is
> > going to disable ODBC and thin .NET clients as well.
> >
> > I believe, we should add options to disable/enable every single client,
> > supported by the ClientListenerProcessor separately. Maybe we should
> > add such options to the SqlConnectorConfiguration.
> >
> > What do you guys think?
> >
> > Best Regards,
> > Igor
> >
>

[Igor Sapego-2]

I've filed a ticket for that: [1]

[1] - https://issues.apache.org/jira/browse/IGNITE-6456

Best Regards,
Igor

On Wed, Sep 20, 2017 at 2:33 PM, Vladimir Ozerov <[hidden email]>
wrote:

> Agree. Do we have a ticket for this?
>
> On Wed, Sep 20, 2017 at 1:27 PM, Pavel Tupitsyn <[hidden email]>
> wrote:
>
> > Yes, I think it would make sense to add enableJdbc, enableOdbc,
> > enableThinClients
> > properties to ClientConnectorConfiguration (which replaces
> > SqlConnectorConfiguration).
> >
> > This way users will also have better understanding of the
> > ClientConnectorConfiguration purpose.
> >
> > Pavel
> >
> > On Wed, Sep 20, 2017 at 1:12 PM, Igor Sapego <[hidden email]> wrote:
> >
> > > Hi, Igniters,
> > >
> > > In current approach, ODBC, thin JDBC and thin .NET client all connect
> > > to the grid using ClientListenerProcessor, which listen on a single
> port.
> > >
> > > The problem is that there is currently no way to disable only one
> client.
> > > For example, currently you can't disallow thin JDBC driver connectivity
> > > alone, you can only disable the whole ClientListenerProcessor, which is
> > > going to disable ODBC and thin .NET clients as well.
> > >
> > > I believe, we should add options to disable/enable every single client,
> > > supported by the ClientListenerProcessor separately. Maybe we should
> > > add such options to the SqlConnectorConfiguration.
> > >
> > > What do you guys think?
> > >
> > > Best Regards,
> > > Igor
> > >
> >
>

[dsetrakyan]

Why do we need the ability to disable individual clients?

On Wed, Sep 20, 2017 at 5:26 AM, Igor Sapego <[hidden email]> wrote:

> I've filed a ticket for that: [1]
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-6456
>
> Best Regards,
> Igor
>
> On Wed, Sep 20, 2017 at 2:33 PM, Vladimir Ozerov <[hidden email]>
> wrote:
>
> > Agree. Do we have a ticket for this?
> >
> > On Wed, Sep 20, 2017 at 1:27 PM, Pavel Tupitsyn <[hidden email]>
> > wrote:
> >
> > > Yes, I think it would make sense to add enableJdbc, enableOdbc,
> > > enableThinClients
> > > properties to ClientConnectorConfiguration (which replaces
> > > SqlConnectorConfiguration).
> > >
> > > This way users will also have better understanding of the
> > > ClientConnectorConfiguration purpose.
> > >
> > > Pavel
> > >
> > > On Wed, Sep 20, 2017 at 1:12 PM, Igor Sapego <[hidden email]>
> wrote:
> > >
> > > > Hi, Igniters,
> > > >
> > > > In current approach, ODBC, thin JDBC and thin .NET client all connect
> > > > to the grid using ClientListenerProcessor, which listen on a single
> > port.
> > > >
> > > > The problem is that there is currently no way to disable only one
> > client.
> > > > For example, currently you can't disallow thin JDBC driver
> connectivity
> > > > alone, you can only disable the whole ClientListenerProcessor, which
> is
> > > > going to disable ODBC and thin .NET clients as well.
> > > >
> > > > I believe, we should add options to disable/enable every single
> client,
> > > > supported by the ClientListenerProcessor separately. Maybe we should
> > > > add such options to the SqlConnectorConfiguration.
> > > >
> > > > What do you guys think?
> > > >
> > > > Best Regards,
> > > > Igor
> > > >
> > >
> >
>

[Igor Sapego-2]

For example, some users may want to disable clients they are not
using due to security considerations.

Best Regards,
Igor

On Wed, Sep 20, 2017 at 4:13 PM, Dmitriy Setrakyan <[hidden email]>
wrote:

> Why do we need the ability to disable individual clients?
>
> On Wed, Sep 20, 2017 at 5:26 AM, Igor Sapego <[hidden email]> wrote:
>
> > I've filed a ticket for that: [1]
> >
> > [1] - https://issues.apache.org/jira/browse/IGNITE-6456
> >
> > Best Regards,
> > Igor
> >
> > On Wed, Sep 20, 2017 at 2:33 PM, Vladimir Ozerov <[hidden email]>
> > wrote:
> >
> > > Agree. Do we have a ticket for this?
> > >
> > > On Wed, Sep 20, 2017 at 1:27 PM, Pavel Tupitsyn <[hidden email]>
> > > wrote:
> > >
> > > > Yes, I think it would make sense to add enableJdbc, enableOdbc,
> > > > enableThinClients
> > > > properties to ClientConnectorConfiguration (which replaces
> > > > SqlConnectorConfiguration).
> > > >
> > > > This way users will also have better understanding of the
> > > > ClientConnectorConfiguration purpose.
> > > >
> > > > Pavel
> > > >
> > > > On Wed, Sep 20, 2017 at 1:12 PM, Igor Sapego <[hidden email]>
> > wrote:
> > > >
> > > > > Hi, Igniters,
> > > > >
> > > > > In current approach, ODBC, thin JDBC and thin .NET client all
> connect
> > > > > to the grid using ClientListenerProcessor, which listen on a single
> > > port.
> > > > >
> > > > > The problem is that there is currently no way to disable only one
> > > client.
> > > > > For example, currently you can't disallow thin JDBC driver
> > connectivity
> > > > > alone, you can only disable the whole ClientListenerProcessor,
> which
> > is
> > > > > going to disable ODBC and thin .NET clients as well.
> > > > >
> > > > > I believe, we should add options to disable/enable every single
> > client,
> > > > > supported by the ClientListenerProcessor separately. Maybe we
> should
> > > > > add such options to the SqlConnectorConfiguration.
> > > > >
> > > > > What do you guys think?
> > > > >
> > > > > Best Regards,
> > > > > Igor
> > > > >
> > > >
> > >
> >
>

[dsetrakyan]

On Wed, Sep 20, 2017 at 6:37 AM, Igor Sapego <[hidden email]> wrote:

> For example, some users may want to disable clients they are not
> using due to security considerations.
>

Well, there should be some authentication command in the protocol, which
will ask a client to login. Ignite should also provide a connection
callback of some sort, which can return false to reject the connection.
This way users will be able to implement there own authentication mechanism
in the callback and stop unwanted clients from connecting.