Skip to content

Support new authentication mechanisms #269

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
DifferentialOrange opened this issue Dec 1, 2022 · 4 comments · Fixed by #273
Closed

Support new authentication mechanisms #269

DifferentialOrange opened this issue Dec 1, 2022 · 4 comments · Fixed by #273
Assignees
Labels
feature A new functionality

Comments

@DifferentialOrange
Copy link
Member

New authentication mechanisms are in design for next Tarantool versions. After the release of this feature, we must support it.

@DifferentialOrange DifferentialOrange added feature A new functionality teamE labels Dec 1, 2022
@DifferentialOrange
Copy link
Member Author

@LeonidVas
Copy link

To be implemented in the EE-version of the connector.

@DifferentialOrange
Copy link
Member Author

So should we close the issue here?

@LeonidVas
Copy link

The bosses turn the wheel one more time. We implement this feature here.

DifferentialOrange added a commit that referenced this issue Dec 24, 2022
Since Tarantool master 2574ff1a configuring authentication type is
supported [1-2]. Together with this, Tarantool EE had introduced
pap-sha256 authentication method support [3-4]. It can be used only
together with SSL transport. To configure, use `auth_type` option in
Connection, MeshConnection or ConnectionPool.

Newest master (there is no dev build in customer zone yet) supports
providing authentication method via IPROTO_ID response. So in this patch
we also move ID request to be executed before authentication.

1. tarantool/tarantool#7988
2. tarantool/tarantool#7989
3. tarantool/tarantool-ee#295
4. tarantool/tarantool-ee#322

Closes #269
DifferentialOrange added a commit that referenced this issue Dec 24, 2022
Since Tarantool master 2574ff1a configuring authentication type is
supported [1-2]. Together with this, Tarantool EE had introduced
pap-sha256 authentication method support [3-4]. It can be used only
together with SSL transport. To configure, use `auth_type` option in
Connection, MeshConnection or ConnectionPool.

Newest master (there is no dev build in customer zone yet) supports
providing authentication method via IPROTO_ID response. So in this patch
we also move ID request to be executed before authentication.

1. tarantool/tarantool#7988
2. tarantool/tarantool#7989
3. tarantool/tarantool-ee#295
4. tarantool/tarantool-ee#322

Closes #269
DifferentialOrange added a commit that referenced this issue Dec 26, 2022
Since Tarantool master 2574ff1a configuring authentication type is
supported [1-2]. Together with this, Tarantool EE had introduced
pap-sha256 authentication method support [3-4]. It can be used only
together with SSL transport. To configure, use `auth_type` option in
Connection, MeshConnection or ConnectionPool.

Newest master (there is no dev build in customer zone yet) supports
providing authentication method via IPROTO_ID response. So in this patch
we also move ID request to be executed before authentication.

1. tarantool/tarantool#7988
2. tarantool/tarantool#7989
3. tarantool/tarantool-ee#295
4. tarantool/tarantool-ee#322

Closes #269
DifferentialOrange added a commit that referenced this issue Dec 26, 2022
Since Tarantool master 2574ff1a configuring authentication type is
supported [1-2]. Together with this, Tarantool EE had introduced
pap-sha256 authentication method support [3-4]. It can be used only
together with SSL transport. To configure, use `auth_type` option in
Connection, MeshConnection or ConnectionPool.

Newest master (there is no dev build in customer zone yet) supports
providing authentication method via IPROTO_ID response. So in this patch
we also move ID request to be executed before authentication.

1. tarantool/tarantool#7988
2. tarantool/tarantool#7989
3. tarantool/tarantool-ee#295
4. tarantool/tarantool-ee#322

Closes #269
DifferentialOrange added a commit that referenced this issue Dec 27, 2022
If encoding=None is used (or similar decoder configuration),
authentication method received in IPROTO_ID response is not a str, but
a bytes object, which is unexpected. This patch fixed the behavior.

Follows #269
DifferentialOrange added a commit that referenced this issue Dec 27, 2022
If encoding=None is used (or similar decoder configuration),
authentication method received in IPROTO_ID response is not an str, but
a bytes object, which is unexpected. This patch fixed the behavior.

Follows #269
DifferentialOrange added a commit that referenced this issue Dec 27, 2022
Use SDK with Tarantool which supports auth method in IPROTO_ID
response [1].

1. tarantool/tarantool@13b0ce9

Follows #269
DifferentialOrange added a commit that referenced this issue Dec 27, 2022
If encoding=None is used (or similar decoder configuration),
authentication method received in IPROTO_ID response is not an str, but
a bytes object, which is unexpected. This patch fixed the behavior.

Follows #269
DifferentialOrange added a commit that referenced this issue Dec 27, 2022
Use SDK with Tarantool which supports auth method in IPROTO_ID
response [1].

1. tarantool/tarantool@13b0ce9

Follows #269
DifferentialOrange added a commit that referenced this issue Dec 30, 2022
Overview

  This release introduces the support of crud module API, encoding and
  decoding customization and various security features for Tarantool EE.

Breaking changes

  This release should not break any existing behavior.

New features
  - Support custom packer and unpacker factories (#191).
  - Support [crud module](https://github.com/tarantool/crud) native API
    (#205).
  - Support `ssl_password` and `ssl_password_file` options
    to decrypt private SSL key file (#224).
  - Support specifying authentication method with `auth_type`
    and Tarantool EE `pap-sha256` authentication method (#269).
DifferentialOrange added a commit that referenced this issue Dec 30, 2022
Overview

  This release introduces the support of crud module API, encoding and
  decoding customization and various security features for Tarantool EE.

Breaking changes

  This release should not break any existing behavior.

New features
  - Support custom packer and unpacker factories (#191).
  - Support [crud module](https://github.com/tarantool/crud) native API
    (#205).
  - Support `ssl_password` and `ssl_password_file` options
    to decrypt private SSL key file (#224).
  - Support specifying authentication method with `auth_type`
    and Tarantool EE `pap-sha256` authentication method (#269).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A new functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants