-
Notifications
You must be signed in to change notification settings - Fork 12k
[ISSUE #10498] Update ACL documentation to include required 5.x properties #10499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
SummCoder
wants to merge
1
commit into
apache:develop
Choose a base branch
from
SummCoder:doc-update-acl-5x-config
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+16
−2
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -34,7 +34,8 @@ ACL客户端可以参考:**org.apache.rocketmq.example.simple**包下面的**A | |
| 具体可以参考**distribution/conf/plain_acl.yml**配置文件 | ||
|
|
||
| ## 3. 支持权限控制的集群部署 | ||
| 在**distribution/conf/plain_acl.yml**配置文件中按照上述说明定义好权限属性后,打开**aclEnable**开关变量即可开启RocketMQ集群的ACL特性。这里贴出Broker端开启ACL特性的properties配置文件内容: | ||
| 在**distribution/conf/plain_acl.yml**配置文件中按照上述说明定义好权限属性后,在Broker配置文件中设置以下属性即可开启RocketMQ集群的ACL特性: | ||
|
|
||
| ``` | ||
| brokerClusterName=DefaultCluster | ||
| brokerName=broker-a | ||
|
|
@@ -48,6 +49,12 @@ storePathCommitLog=/data/rocketmq/commitlog-a-m | |
| autoCreateSubscriptionGroup=true | ||
| ## if acl is open,the flag will be true | ||
| aclEnable=true | ||
| ## RocketMQ 5.x 需要额外配置以下ACL属性 | ||
| authenticationEnabled=true | ||
| authorizationEnabled=true | ||
| migrateAuthFromV1Enabled=true | ||
| authenticationMetadataProvider=org.apache.rocketmq.auth.authentication.provider.LocalAuthenticationMetadataProvider | ||
| authorizationMetadataProvider=org.apache.rocketmq.auth.authorization.provider.LocalAuthorizationMetadataProvider | ||
| listenPort=10911 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe we should also add the default authentication and authorization providers here for completeness: |
||
| brokerIP1=XX.XX.XX.XX1 | ||
| namesrvAddr=XX.XX.XX.XX:9876 | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -33,7 +33,8 @@ The definition of Topic resource access control for RocketMQ is mainly as shown | |
| For details, please refer to the **distribution/conf/plain_acl.yml** configuration file. | ||
|
|
||
| ## 3. Cluster deployment with permission control | ||
| After defining the permission attribute in the **distribution/conf/plain_acl.yml** configuration file as described above, open the **aclEnable** switch variable to enable the ACL feature of the RocketMQ cluster.The configuration file of the ACL feature enabled on the broker is as follows: | ||
| After defining the permission attribute in the **distribution/conf/plain_acl.yml** configuration file as described above, enable the ACL feature by setting the following properties in the broker configuration file: | ||
|
|
||
| ```properties | ||
| brokerClusterName=DefaultCluster | ||
| brokerName=broker-a | ||
|
|
@@ -47,6 +48,12 @@ storePathCommitLog=/data/rocketmq/commitlog-a-m | |
| autoCreateSubscriptionGroup=true | ||
| ## if acl is open,the flag will be true | ||
| aclEnable=true | ||
| ## RocketMQ 5.x requires the following additional ACL properties | ||
| authenticationEnabled=true | ||
| authorizationEnabled=true | ||
| migrateAuthFromV1Enabled=true | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ditto. |
||
| authenticationMetadataProvider=org.apache.rocketmq.auth.authentication.provider.LocalAuthenticationMetadataProvider | ||
| authorizationMetadataProvider=org.apache.rocketmq.auth.authorization.provider.LocalAuthorizationMetadataProvider | ||
| listenPort=10911 | ||
| brokerIP1=XX.XX.XX.XX1 | ||
| namesrvAddr=XX.XX.XX.XX:9876 | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think
migrateAuthFromV1Enabledis not necessary here, since it is only required when migrating from ACL v1 to ACL v2.