Change structure of config to adhere to latest implemented version of the config_manager

Author: Anna-Rehm

Images/qiita/config_qiita_oidc.cfg

@@ -17,7 +17,7 @@ TEST_ENVIRONMENT = TRUE
 
 # Absolute path to the directory where log files are saved. If not given, no
 # log file will be created
-LOG_DIR =
+LOG_DIR = /qiita/
 
 # Whether studies require admin approval to be made available
 REQUIRE_APPROVAL = True
@@ -201,8 +201,8 @@ QIIMP = https://localhost:8898/
 # --------------------- External Identity Provider settings --------------------
 # user authentication happens per default within Qiita, i.e. when a user logs in,
 # the stored password hash and email address is compared against what a user
-# just provided. You might however, use an external identity provider (IdP) to 
-# authenticate the user like 
+# just provided. You might however, use an external identity provider (IdP) to
+# authenticate the user like
 #    google: https://developers.google.com/identity/protocols/oauth2 or
 #    github: https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/authorizing-oauth-apps or
 #    self hosted keycloak: https://www.keycloak.org/
@@ -226,33 +226,40 @@ QIIMP = https://localhost:8898/
 # 3) you obtain information about the user for the obtaines user token
 # Typically, each step is implemented as a separate URL endpoint
 #
-# To activate IdP: remove comments from the following config section
-
-#[oidc_localkeycloak]
+# To activate IdP: comment out the following config section
 
+# [oidc_localkeycloak]
+#
 ## client ID for Qiita as registered at your Identity Provider of choice
-#CLIENT_ID = qiita
-
+# CLIENT_ID = qiita
+#
 ## client secret to verify Qiita as the correct client. Not all IdPs require
 ## a client secret!
-## ADD CLIENT SECRET FROM YOUR LOCAL KEYCLOAK
-#CLIENT_SECRET = 
+# CLIENT_SECRET = supersecretString
 
-## redirect URL (end point in your Qiita instance), to which the IdP redirects 
-## after user types in his/her credentials. If you don't want to change code in 
+#
+## redirect URL (end point in your Qiita instance), to which the IdP redirects
+## after user types in his/her credentials. If you don't want to change code in
 ## qiita_pet/webserver.py the URL must follow the pattern:
-## base_URL/auth/login_OIDC/foo where foo is the name of this config section 
+## base_URL/auth/login_OIDC/foo where foo is the name of this config section
 ## without the oidc_ prefix!
-#REDIRECT_ENDPOINT = /auth/login_OIDC/localkeycloak
-
-## URL for step 1: obtain code
-#AUTHORIZE_URL = http://localhost:8080/realms/qiita_realm/protocol/openid-connect/auth
-
-## URL for step 2: obtain user token
-#ACCESS_TOKEN_URL = http://localhost:8080/realms/qiita_realm/protocol/openid-connect/token
-
-## URL for step 3: obtain user infos
-#USERINFO_URL = http://localhost:8080/realms/qiita_realm/protocol/openid-connect/userinfo
-
+# REDIRECT_ENDPOINT = /auth/login_OIDC/localkeycloak
+#
+## The URL of the well-known json document, specifying how API end points
+## like 'authorize', 'token' or 'userinfo' are defined. See e.g.
+## https://swagger.io/docs/specification/authentication/
+##    openid-connect-discovery/
+# WELLKNOWN_URI = http://localhost:9999/realms/qiita_realm/.well-known/openid-configuration
+#
 ## a speaking label for the Identity Provider. Section name is used if empty.
-#LABEL = localhost
+# LABEL = localkeycloak
+#
+## The scope, i.e. fields about a user, which Qiita requests from the
+## Identity Provider, e.g. "profile email eduperson_orcid".
+## Will be automatically extended by the scope "openid", to enable the
+## "authorize_code" OIDC flow.
+# SCOPE = openid
+#
+##Optional. Name of a file in qiita_pet/static/img that shall be
+##displayed for login through Service Provider, instead of a plain button
+# LOGO =