kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [kafka] branch trunk updated: MINOR: Fix 404 security features links (#6634)
Date Thu, 25 Apr 2019 16:06:04 GMT
This is an automated email from the ASF dual-hosted git repository.

jgus 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 96e1fd6  MINOR: Fix 404 security features links (#6634)
96e1fd6 is described below

commit 96e1fd6cc7ec6af2f688fc4641bdd6d6b608835b
Author: pierDipi <33736985+pierDipi@users.noreply.github.com>
AuthorDate: Thu Apr 25 18:05:43 2019 +0200

    MINOR: Fix 404 security features links (#6634)
    
    Reviewers: Jason Gustafson <jason@confluent.io>
---
 docs/streams/developer-guide/security.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/streams/developer-guide/security.html b/docs/streams/developer-guide/security.html
index 821a34e..29b7c2b 100644
--- a/docs/streams/developer-guide/security.html
+++ b/docs/streams/developer-guide/security.html
@@ -40,7 +40,7 @@
                 <li><a class="reference internal" href="#security-example" id="id2">Security
example</a></li>
             </ul>
         </div>
-        <p>Kafka Streams natively integrates with the <a class="reference internal"
href="../../kafka/security.html#kafka-security"><span class="std std-ref">Kafka&#8217;s
security features</span></a> and supports all of the
+        <p>Kafka Streams natively integrates with the <a class="reference internal"
href="../../documentation.html#security"><span class="std std-ref">Kafka&#8217;s
security features</span></a> and supports all of the
             client-side security features in Kafka.  Streams leverages the <a class="reference
internal" href="../../clients/index.html#kafka-clients"><span class="std std-ref">Java
Producer and Consumer API</span></a>.</p>
         <p>To secure your Stream processing applications, configure the security settings
in the corresponding Kafka producer
             and consumer clients, and then specify the corresponding configuration settings
in your Kafka Streams application.</p>
@@ -61,7 +61,7 @@
                 that only specific applications are allowed to read from a Kafka topic. 
You can also restrict write access to Kafka
                 topics to prevent data pollution or fraudulent activities.</dd>
         </dl>
-        <p>For more information about the security features in Apache Kafka, see <a
class="reference internal" href="../../kafka/security.html#kafka-security"><span class="std
std-ref">Kafka Security</span></a>.</p>
+        <p>For more information about the security features in Apache Kafka, see <a
class="reference internal" href="../../documentation.html#security"><span class="std
std-ref">Kafka Security</span></a>.</p>
         <div class="section" id="required-acl-setting-for-secure-kafka-clusters">
             <span id="streams-developer-guide-security-acls"></span><h2><a
class="toc-backref" href="#id1">Required ACL setting for secure Kafka clusters</a><a
class="headerlink" href="#required-acl-setting-for-secure-kafka-clusters" title="Permalink
to this headline"></a></h2>
             <p>Kafka clusters can use ACLs to control access to resources (like the
ability to create topics), and for such clusters each client,


Mime
View raw message