(kafka) branch trunk updated: MINOR: Fix url in streams security site (#23562)

[fr...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

frankvicky pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/trunk by this push:
     new 7aba83304c6 MINOR: Fix url in streams security site (#23562)
7aba83304c6 is described below

commit 7aba83304c69e151597ecfb4e8a004079cdd1ec8
Author: TengYao Chi <fr...@apache.org>
AuthorDate: Wed Sep 23 13:47:04 2026 +0100

    MINOR: Fix url in streams security site (#23562)
    
    Fix the 404 error for two urls, `internal topics` and `application id`
    
    Before:
    
    `.../43/streams/developer-guide/security/manage-topics.html#streams-developer-guide-topics-internal`
    
    `.../43/documentation/streams/developer-guide/config-streams.html#required-configuration-parameters`
    After:  `.../43/streams/developer-guide/manage-topics/#internal-topics`
    
    `.../43/streams/developer-guide/config-streams/#required-configuration-parameters`
    
    Reviewers: Lucas Brutschy <lb...@confluent.io>
---
 docs/streams/developer-guide/security.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/streams/developer-guide/security.md b/docs/streams/developer-guide/security.md
index 90877913b67..2a0ea06c217 100644
--- a/docs/streams/developer-guide/security.md
+++ b/docs/streams/developer-guide/security.md
@@ -48,7 +48,7 @@ For more information about the security features in Apache Kafka, see [Kafka Sec
 
 # Required ACL setting for secure Kafka clusters
 
-Kafka clusters can use ACLs to control access to resources (like the ability to create topics), and for such clusters each client, including Kafka Streams, is required to authenticate as a particular user in order to be authorized with appropriate access. In particular, when Streams applications are run against a secured Kafka cluster, the principal running the application must have the ACL set so that the application has the permissions to create, read and write [internal topics](../man [...]
+Kafka clusters can use ACLs to control access to resources (like the ability to create topics), and for such clusters each client, including Kafka Streams, is required to authenticate as a particular user in order to be authorized with appropriate access. In particular, when Streams applications are run against a secured Kafka cluster, the principal running the application must have the ACL set so that the application has the permissions to create, read and write [internal topics](../man [...]
 
 If the [streams rebalance protocol](https://cwiki.apache.org/confluence/display/KAFKA/KIP-1071%3A+Streams+Rebalance+Protocol) is enabled by setting `group.protocol=streams`, the following ACLs are required on the topic and group resources:  
   
@@ -161,7 +161,7 @@ Required for all topics used in the group's topology
 
 As mentioned earlier, Kafka Streams applications need appropriate ACLs to create internal topics when running against a secured Kafka cluster. To avoid providing this permission to your application, you can create the required internal topics manually. If the internal topics exist, Kafka Streams will not try to recreate them. Note, that the internal repartition and changelog topics must be created with the correct number of partitions--otherwise, Kafka Streams will fail on startup. The t [...]
 
-Since all internal topics as well as the embedded consumer group name are prefixed with the [application id](/43/documentation/streams/developer-guide/config-streams.html#required-configuration-parameters), it is recommended to use ACLs on prefixed resource pattern to configure control lists to allow client to manage all topics and consumer groups started with this prefix as `--resource-pattern-type prefixed --topic your.application.id --operation All ` (see [KIP-277](https://cwiki.apach [...]
+Since all internal topics as well as the embedded consumer group name are prefixed with the [application id](../config-streams#required-configuration-parameters), it is recommended to use ACLs on prefixed resource pattern to configure control lists to allow client to manage all topics and consumer groups started with this prefix as `--resource-pattern-type prefixed --topic your.application.id --operation All ` (see [KIP-277](https://cwiki.apache.org/confluence/x/zlOHB) and [KIP-290](http [...]
 
 # Security example