[
https://issues.apache.org/jira/browse/IGNITE-19365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-19365:
-------------------------------
Description:
There are instances where the Ignite 3 component requires to be "enabled" when
the cluster configuration is applied. The lifecycle of the component can be
adjusted to follow these steps: creating the component, starting the component,
*waiting for the required cluster configuration, and enabling the component*.
One particular example is the REST component, which needs to be configured with
basic authentication. There is a time-lapse between cluster initialization and
applying the authentication configuration. During this time, the REST API
remains unauthenticated, and the cluster endpoints are available to everyone,
as mentioned in the IGNITE-18943 ticket. The component needs to be started ->
the cluster must be initialized -> but basic auth cluster configuration should
be applied -> REST is enabled.
Redesign of the Ignite 3 component lifecycle is a part of this issue.
was:
There are instances where the Ignite 3 component requires to be "enabled" when
the cluster configuration is applied. The lifecycle of the component can be
adjusted to follow these steps: creating the component, starting the component,
*waiting for the required cluster configuration, and enabling the component*.
One particular example is the REST component, which needs to be configured with
basic authentication. There is a time-lapse between cluster initialization and
applying the authentication configuration. During this time, the REST API
remains unauthenticated, and the cluster endpoints are available to everyone,
as mentioned in the IGNITE-18943 ticket. To address this issue, the component
needs to be started, the cluster must be initialized, but basic auth
configuration should not be applied until the cluster endpoints are
authenticated, and finally, the basic authentication configuration should be
applied, enabling the authentication to work properly.
Redesign of the Ignite 3 component lifecycle is a part of this issue.
> Disable components until the cluster configuration is applied
> -------------------------------------------------------------
>
> Key: IGNITE-19365
> URL: https://issues.apache.org/jira/browse/IGNITE-19365
> Project: Ignite
> Issue Type: New Feature
> Components: clients, rest
> Reporter: Vadim Pakhnushev
> Priority: Major
> Labels: ignite-3
>
> There are instances where the Ignite 3 component requires to be "enabled"
> when the cluster configuration is applied. The lifecycle of the component can
> be adjusted to follow these steps: creating the component, starting the
> component, *waiting for the required cluster configuration, and enabling the
> component*.
> One particular example is the REST component, which needs to be configured
> with basic authentication. There is a time-lapse between cluster
> initialization and applying the authentication configuration. During this
> time, the REST API remains unauthenticated, and the cluster endpoints are
> available to everyone, as mentioned in the IGNITE-18943 ticket. The component
> needs to be started -> the cluster must be initialized -> but basic auth
> cluster configuration should be applied -> REST is enabled.
> Redesign of the Ignite 3 component lifecycle is a part of this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
