[
https://issues.apache.org/jira/browse/IGNITE-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Filatov updated IGNITE-14023:
-------------------------------------
Description:
Should be able to write tests with authentication enabled for built-in
authentication
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running the Ignite node and application with third-party authentication remains
to be implemented by the developers of this 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
for default parameters: -gj '\{"use_auth":"True"}'
to pass parameters explicitly: -gj '\{"use_auth":"True",
"admin":{"login":"admin1","password":"qwe123"}}'
for a cluster with enabled ssl and authentication: -gj
'\{"use_ssl":"True","use_auth":"True"}'
for a cluster with enabled ssl and authentication: -gj
'\{"use_ssl":"True","use_auth":"True","admin":{"login":"admin1","password":"qwe123","ssl":{"key_store_jks":"admin1.jks","key_store_password":"qwe123","trust_store_jks":truststore.jks","trust_store_password":"qwe123"}}}'
was:
Authentication usage in ducktape tests
If we have cluster with enabled authentication we need to provide
authentication parameters to controls.sh utility
Necessary:
- tests should work on cluster with enabled authentication
- be able to write tests with authentication enabled
- be able to enable authentication for all tests via globals.
- be able to set the authentication parameters for tests via globals.
for run all tests with authentication you may use globals:
> 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
>
> Should be able to write tests with authentication enabled for built-in
> authentication
> Tests should work if authentication is enabled on the cluster via a
> third-party plugin
> Running the Ignite node and application with third-party authentication
> remains to be implemented by the developers of this 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
> for default parameters: -gj '\{"use_auth":"True"}'
> to pass parameters explicitly: -gj '\{"use_auth":"True",
> "admin":{"login":"admin1","password":"qwe123"}}'
> for a cluster with enabled ssl and authentication: -gj
> '\{"use_ssl":"True","use_auth":"True"}'
> for a cluster with enabled ssl and authentication: -gj
> '\{"use_ssl":"True","use_auth":"True","admin":{"login":"admin1","password":"qwe123","ssl":{"key_store_jks":"admin1.jks","key_store_password":"qwe123","trust_store_jks":truststore.jks","trust_store_password":"qwe123"}}}'
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
