You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (Jira)" <ji...@apache.org> on 2021/03/05 09:25:00 UTC
[jira] [Updated] (IGNITE-14023) Password based authentication
support in ducktape tests
[ https://issues.apache.org/jira/browse/IGNITE-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anton Vinogradov updated IGNITE-14023:
--------------------------------------
Sprint: Ducktape Sprint 1, Ducktape Sprint 2, Ducktape Sprint 3, Ducktape Sprint 4, Ducktape Sprint 5 (was: Ducktape Sprint 1, Ducktape Sprint 2, Ducktape Sprint 3, Ducktape Sprint 4)
> Password based authentication support in ducktape tests
> -------------------------------------------------------
>
> Key: IGNITE-14023
> URL: https://issues.apache.org/jira/browse/IGNITE-14023
> Project: Ignite
> Issue Type: Task
> Reporter: Mikhail Filatov
> Assignee: Mikhail Filatov
> Priority: Minor
> Time Spent: 9h 20m
> Remaining Estimate: 0h
>
> There are users with authentication enabled on the cluster
> Ducktape tests should work on such clusters.
> Tests should work if authentication is enabled on the cluster via a third-party plugin
> Running Ignite node and application with third-party authentication plugin remains to be implemented by the developers of that plugin.
> In this PR we will only implement the ability to tell control.sh how to connect to the cluster.
> connection parameters should be passed through globals with structure like that.
> {
> "use_ssl": True,
> "admin": {
> "credentials": ["username", "qwerty_123"],
> "ssl": {
> "key_store_jks": ....
> }
> }
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)