From 30fbee5528acf4fb468e474000ef734d49ea7054 Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
Date: Tue, 28 Nov 2023 10:09:42 -0600
Subject: [PATCH] Revert "Including info on OpenID Additional Parameters
 (#5600)" (#5686)

This reverts commit 4af8a0dda5a610844a8a506eaf451beb40ba10dc.
---
 _security/authentication-backends/openid-connect.md | 13 -------------
 1 file changed, 13 deletions(-)

diff --git a/_security/authentication-backends/openid-connect.md b/_security/authentication-backends/openid-connect.md
index 4e6eb427e8f..2ff75a3cf84 100755
--- a/_security/authentication-backends/openid-connect.md
+++ b/_security/authentication-backends/openid-connect.md
@@ -336,19 +336,6 @@ opensearch.requestHeadersAllowlist: ["Authorization", "security_tenant"]
 To include OpenID Connect with other authentication types in the Dashboards sign-in window, see [Configuring sign-in options]({{site.url}}{{site.baseurl}}/security/configuration/multi-auth/).
 {: .note } 
 
-### Additional parameters
-
-Some identity providers require custom parameters to complete the authentication process. You can add custom parameters `opensearch_dashboards.yml` configuration file  under the `opensearch_security.openid.additional_parameters` namespace. You can find these additional parameters by making a GET request to your identity provider. This feature allows for greater flexibility and customization when communicating with various identity providers.
-
-In the following example, two custom parameters, `foo` and `acr_values`, and their values, `bar` and `1`, were found using a GET request to OpenID provider:
-
-```yml
-opensearch_security.openid.additional_parameters.foo: "bar"
-opensearch_security.openid.additional_parameters.acr_values: "1"
-```
-{% include copy.html %}
-
-
 
 #### Session management with additional cookies