From 53c79e87ca53246c5c7e57ae84abf1b7c7c8c73e Mon Sep 17 00:00:00 2001 From: okumin Date: Sun, 5 Aug 2018 01:12:06 +0900 Subject: [PATCH] HADOOP-15652. Fix typos SPENGO into SPNEGO --- .../authentication/server/MultiSchemeAuthenticationHandler.java | 2 +- .../src/main/java/org/apache/hadoop/log/LogLevel.java | 2 +- .../web/MultiSchemeDelegationTokenAuthenticationHandler.java | 2 +- hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/WebHDFS.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/server/MultiSchemeAuthenticationHandler.java b/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/server/MultiSchemeAuthenticationHandler.java index 58a0adb237e70..5fc668e2ce568 100644 --- a/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/server/MultiSchemeAuthenticationHandler.java +++ b/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/server/MultiSchemeAuthenticationHandler.java @@ -36,7 +36,7 @@ /** * The {@link MultiSchemeAuthenticationHandler} supports configuring multiple * authentication mechanisms simultaneously. e.g. server can support multiple - * authentication mechanisms such as Kerberos (SPENGO) and LDAP. During the + * authentication mechanisms such as Kerberos (SPNEGO) and LDAP. During the * authentication phase, server will specify all possible authentication schemes * and let client choose the appropriate scheme. Please refer to RFC-2616 and * HADOOP-12082 for more details. diff --git a/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java b/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java index 79eae12314493..e506987207a11 100644 --- a/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java +++ b/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java @@ -282,7 +282,7 @@ private URLConnection connect(URL url) throws Exception { /** * Configures the client to send HTTP/HTTPS request to the URL. - * Supports SPENGO for authentication. + * Supports SPNEGO for authentication. * @param urlString URL and query string to the daemon's web UI * @throws Exception if unable to connect */ diff --git a/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/token/delegation/web/MultiSchemeDelegationTokenAuthenticationHandler.java b/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/token/delegation/web/MultiSchemeDelegationTokenAuthenticationHandler.java index fc32a19d1fdd9..79acc81983a94 100644 --- a/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/token/delegation/web/MultiSchemeDelegationTokenAuthenticationHandler.java +++ b/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/token/delegation/web/MultiSchemeDelegationTokenAuthenticationHandler.java @@ -42,7 +42,7 @@ * A {@link CompositeAuthenticationHandler} that supports multiple HTTP * authentication schemes along with Delegation Token functionality. e.g. * server can support multiple authentication mechanisms such as Kerberos - * (SPENGO) and LDAP. During the authentication phase, server will specify + * (SPNEGO) and LDAP. During the authentication phase, server will specify * all possible authentication schemes and let client choose the appropriate * scheme. Please refer to RFC-2616 and HADOOP-12082 for more details. * diff --git a/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/WebHDFS.md b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/WebHDFS.md index eb1181581e55c..e9aa5d1d91a24 100644 --- a/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/WebHDFS.md +++ b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/WebHDFS.md @@ -134,7 +134,7 @@ Additionally, WebHDFS supports OAuth2 on the client side. The Namenode and Datan WebHDFS supports two type of OAuth2 code grants (user-provided refresh and access token or user provided credential) by default and provides a pluggable mechanism for implementing other OAuth2 authentications per the [OAuth2 RFC](https://tools.ietf.org/html/rfc6749), or custom authentications. When using either of the provided code grant mechanisms, the WebHDFS client will refresh the access token as necessary. -OAuth2 should only be enabled for clients not running with Kerberos SPENGO. +OAuth2 should only be enabled for clients not running with Kerberos SPNEGO. | OAuth2 code grant mechanism | Description | Value of `dfs.webhdfs.oauth2.access.token.provider` that implements code grant | |:---- |:---- |:----|