[
https://issues.apache.org/jira/browse/IGNITE-15969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-15969:
-----------------------------------
Description:
When you start cluster with turned on built-in authentication it requires to
enable persistence too [1].
This requirement seems to be useless for client nodes, because they has no
persistence, but without pesistence client node would fail during start up with
below error:
{code}
class org.apache.ignite.IgniteCheckedException: Authentication can be enabled
only for cluster with enabled persistence. Check the DataRegionConfiguration
at
org.apache.ignite.internal.processors.authentication.IgniteAuthenticationProcessor.startProcessor(IgniteAuthenticationProcessor.java:166)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1259)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2141)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1787)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1172)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:642)
{code}
Reproducer: [^ClientNodeAuthFailureReproducer.patch]
Links:
https://ignite.apache.org/docs/latest/security/authentication
was:
When you start cluster with turned on built-in authentication it requires to
enable persistence too [1].
This requirement seems to be useless for client nodes, because they has no
persistence, but without pesistence client node would fail during start up with
below error:
{code}
class org.apache.ignite.IgniteCheckedException: Authentication can be enabled
only for cluster with enabled persistence. Check the DataRegionConfiguration
at
org.apache.ignite.internal.processors.authentication.IgniteAuthenticationProcessor.startProcessor(IgniteAuthenticationProcessor.java:166)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1259)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2141)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1787)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1172)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:642)
{code}
Links:
https://ignite.apache.org/docs/latest/security/authentication
> Enabling authentication requires the client node to enable persistence in the
> configuration
> -------------------------------------------------------------------------------------------
>
> Key: IGNITE-15969
> URL: https://issues.apache.org/jira/browse/IGNITE-15969
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.11
> Reporter: Ilya Shishkov
> Assignee: Ilya Shishkov
> Priority: Minor
> Attachments: ClientNodeAuthFailureReproducer.patch
>
>
> When you start cluster with turned on built-in authentication it requires to
> enable persistence too [1].
> This requirement seems to be useless for client nodes, because they has no
> persistence, but without pesistence client node would fail during start up
> with below error:
> {code}
> class org.apache.ignite.IgniteCheckedException: Authentication can be enabled
> only for cluster with enabled persistence. Check the DataRegionConfiguration
> at
> org.apache.ignite.internal.processors.authentication.IgniteAuthenticationProcessor.startProcessor(IgniteAuthenticationProcessor.java:166)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1259)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2141)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1787)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1172)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:642)
> {code}
> Reproducer: [^ClientNodeAuthFailureReproducer.patch]
> Links:
> https://ignite.apache.org/docs/latest/security/authentication
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
