You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by zh...@apache.org on 2020/08/17 05:56:48 UTC
[flink] branch master updated: [FLINK-18081][doc] Fix broken links
in Kerberos Authentication Setup and Configuration
This is an automated email from the ASF dual-hosted git repository.
zhuzh pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/master by this push:
new e56e7e4 [FLINK-18081][doc] Fix broken links in Kerberos Authentication Setup and Configuration
e56e7e4 is described below
commit e56e7e40f15a86909ecfbbb1fd4a720f94621107
Author: Yangze Guo <ka...@gmail.com>
AuthorDate: Mon Aug 17 11:04:46 2020 +0800
[FLINK-18081][doc] Fix broken links in Kerberos Authentication Setup and Configuration
---
docs/ops/security-kerberos.md | 6 +++---
docs/ops/security-kerberos.zh.md | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/ops/security-kerberos.md b/docs/ops/security-kerberos.md
index 0a831b6b..486c2c1 100644
--- a/docs/ops/security-kerberos.md
+++ b/docs/ops/security-kerberos.md
@@ -83,7 +83,7 @@ Here is some information specific to each deployment mode.
Steps to run a secure Flink cluster in standalone/cluster mode:
-1. Add security-related configuration options to the Flink configuration file (on all cluster nodes) (see [here](config.html#kerberos-based-security)).
+1. Add security-related configuration options to the Flink configuration file (on all cluster nodes) (see [here](config.html#auth-with-external-systems)).
2. Ensure that the keytab file exists at the path indicated by `security.kerberos.login.keytab` on all cluster nodes.
3. Deploy Flink cluster as normal.
@@ -91,7 +91,7 @@ Steps to run a secure Flink cluster in standalone/cluster mode:
Steps to run a secure Flink cluster in YARN/Mesos mode:
-1. Add security-related configuration options to the Flink configuration file on the client (see [here](config.html#kerberos-based-security)).
+1. Add security-related configuration options to the Flink configuration file on the client (see [here](config.html#auth-with-external-systems)).
2. Ensure that the keytab file exists at the path as indicated by `security.kerberos.login.keytab` on the client node.
3. Deploy Flink cluster as normal.
@@ -107,7 +107,7 @@ The main drawback is that the cluster is necessarily short-lived since the gener
Steps to run a secure Flink cluster using `kinit`:
-1. Add security-related configuration options to the Flink configuration file on the client (see [here](config.html#kerberos-based-security)).
+1. Add security-related configuration options to the Flink configuration file on the client (see [here](config.html#auth-with-external-systems)).
2. Login using the `kinit` command.
3. Deploy Flink cluster as normal.
diff --git a/docs/ops/security-kerberos.zh.md b/docs/ops/security-kerberos.zh.md
index 0a831b6b..486c2c1 100644
--- a/docs/ops/security-kerberos.zh.md
+++ b/docs/ops/security-kerberos.zh.md
@@ -83,7 +83,7 @@ Here is some information specific to each deployment mode.
Steps to run a secure Flink cluster in standalone/cluster mode:
-1. Add security-related configuration options to the Flink configuration file (on all cluster nodes) (see [here](config.html#kerberos-based-security)).
+1. Add security-related configuration options to the Flink configuration file (on all cluster nodes) (see [here](config.html#auth-with-external-systems)).
2. Ensure that the keytab file exists at the path indicated by `security.kerberos.login.keytab` on all cluster nodes.
3. Deploy Flink cluster as normal.
@@ -91,7 +91,7 @@ Steps to run a secure Flink cluster in standalone/cluster mode:
Steps to run a secure Flink cluster in YARN/Mesos mode:
-1. Add security-related configuration options to the Flink configuration file on the client (see [here](config.html#kerberos-based-security)).
+1. Add security-related configuration options to the Flink configuration file on the client (see [here](config.html#auth-with-external-systems)).
2. Ensure that the keytab file exists at the path as indicated by `security.kerberos.login.keytab` on the client node.
3. Deploy Flink cluster as normal.
@@ -107,7 +107,7 @@ The main drawback is that the cluster is necessarily short-lived since the gener
Steps to run a secure Flink cluster using `kinit`:
-1. Add security-related configuration options to the Flink configuration file on the client (see [here](config.html#kerberos-based-security)).
+1. Add security-related configuration options to the Flink configuration file on the client (see [here](config.html#auth-with-external-systems)).
2. Login using the `kinit` command.
3. Deploy Flink cluster as normal.