[
https://issues.apache.org/jira/browse/IGNITE-24489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Pakhnushev updated IGNITE-24489:
--------------------------------------
Ignite Flags: (was: Release Notes Required)
> Can't run sql after asking for credentials
> ------------------------------------------
>
> Key: IGNITE-24489
> URL: https://issues.apache.org/jira/browse/IGNITE-24489
> Project: Ignite
> Issue Type: Bug
> Components: cli
> Reporter: Vadim Pakhnushev
> Assignee: Vadim Pakhnushev
> Priority: Major
> Labels: ignite-3
>
> When CLI connects to the cluster with enabled authentication and no
> credentials are saved in the CLI config, it asks the user for credentials,
> then saves them.
> All commands work after that, but {{sql}} fails with the handshake error:
> {noformat}
> [ignite:node]> sql
> 196609 Trace ID: 445e8442-2b90-489e-b1bb-19f406782384
> Connection failed
> Handshake error [endpoint=localhost/<unresolved>:10800]{noformat}
> The issue is when we check the connection in the {{ConnectWizardCall}}, we
> first construct the {{SessionInfo}} in the {{ConnectionChecker}} using
> {{jdbcUrlFactory}} which takes the username/password values from the config
> rather than from the current settings provided by user in the answers.
> Then, we save the values to the config and return the {{SessionInfo}} which
> doesn't contain these parameters.
> After disconnect/connect it works again.
> We should use the properties configured in the {{ConnectionChecker}} on top
> of the config values when constructing the JDBC URL.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
