[
https://issues.apache.org/jira/browse/IGNITE-21832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831407#comment-17831407
]
Ignite TC Bot commented on IGNITE-21832:
----------------------------------------
{panel:title=Branch: [pull/11287/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11287/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Control Utility 2{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7802937]]
* {color:#013220}IgniteControlUtilityTestSuite2:
SecurityCommandHandlerPermissionsTest.testClusterTag[cmdHnd=cli] - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7802943&buildTypeId=IgniteTests24Java8_RunAll]
> Remove permissions check to obtain cluster tag and id via Control Utility.
> --------------------------------------------------------------------------
>
> Key: IGNITE-21832
> URL: https://issues.apache.org/jira/browse/IGNITE-21832
> Project: Ignite
> Issue Type: Task
> Reporter: Nikita Amelchev
> Assignee: Anastasia Iakimova
> Priority: Minor
> Fix For: 2.17
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The cluster tag and ID do not require read permission. It is accessible
> through the public API, but not from control.sh. The user will still need
> ADMIN_OPS permission to change the tag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
