[DX-1722] Deprecation announcement (#5643)

* deprecation

* ODIC

* Update tyk-docs/content/basic-config-and-security/security/authentication-authorization/openid-connect.md

Co-authored-by: andyo-tyk <[email protected]>

* Update tyk-docs/content/basic-config-and-security/security/authentication-authorization/ext-oauth-middleware.md

Co-authored-by: andyo-tyk <[email protected]>

* Update tyk-docs/content/tyk-dashboard/database-options.md

Co-authored-by: andyo-tyk <[email protected]>


* remove odd file

---------

Co-authored-by: andyo-tyk <[email protected]>
Co-authored-by: Yaara <[email protected]>

Author: 3 people

tyk-docs/content/basic-config-and-security/security/authentication-authorization/ext-oauth-middleware.md

@@ -8,6 +8,11 @@ menu:
     parent: "OAuth 2.0"
 weight: 7
 ---
+{{< note success >}}
+**Note**  
+
+Tyk's dedicated External OAuth middleware will be deprecated from Tyk 5.7.0. Tyk's [JSON Web Token (JWT)]({{< ref "basic-config-and-security/security/authentication-authorization/json-web-tokens#about-jwts" >}}) authentication method also allows you to integrate with a third party OAuth provider, so the dedicated middleware will be deprecated to reduce duplication and potential for misconfiguration.
+{{< /note >}}
 
 ## Introduction
 

tyk-docs/content/basic-config-and-security/security/authentication-authorization/openid-connect.md

@@ -14,6 +14,13 @@ aliases:
   - /advanced-configuration/integrate/api-auth-mode/json-web-tokens
 ---
 
+{{< note success >}}
+**Note**  
+
+Tyk's dedicated OpenID Connect Authentication middleware will be deprecated from Tyk 5.7.0. Tyk's [JSON Web Token (JWT)]({{< ref "basic-config-and-security/security/authentication-authorization/json-web-tokens#about-jwts" >}}) authentication method also allows you to integrate with an OIDC provider, so the dedicated OIDC middleware will be deprecated to reduce duplication and potential for misconfiguration.
+{{< /note >}}
+
+
 [OpenID Connect](https://openid.net/developers/how-connect-works) (OIDC) builds on top of OAuth 2.0, adding authentication. You can secure your APIs on Tyk by integrating with any standards compliant OIDC provider using [JSON Web Tokens]({{< ref "basic-config-and-security/security/authentication-authorization/json-web-tokens" >}}) (JWTs).
 JWTs offer a simple way to use the third-party Identity Provider (IdP) without needing any direct integration between the Tyk and 3rd-party systems.
 

tyk-docs/content/product-stack/tyk-charts/tyk-control-plane-chart.md

@@ -771,6 +771,12 @@ tyk-dev-portal:
 
 #### Tyk Developer Portal Database
 
+{{< note success >}}
+**Note** 
+
+SQLite support will be deprecated from Tyk 5.7.0. To avoid disrupution, please transition to PostgreSQL, MongoDB or one of the listed compatible alternatives.
+{{< /note >}}
+
 By default, Tyk Developer Portal use `sqlite3` to store portal metadata. If you want to use a different SQL Database, please modify the section below.
 
 ```yaml

tyk-docs/content/product-stack/tyk-charts/tyk-stack-chart.md

@@ -794,6 +794,12 @@ tyk-dev-portal:
 
 #### Tyk Developer Portal Database
 
+{{< note success >}}
+**Note** 
+
+SQLite support will be deprecated from Tyk 5.7.0. To avoid disrupution, please transition to PostgreSQL, MongoDB or one of the listed compatible alternatives.
+{{< /note >}}
+
 By default, Tyk Developer Portal use `sqlite3` to store portal metadata. If you want to use other SQL Database, please modify the section below.
 
 ```yaml

tyk-docs/content/product-stack/tyk-dashboard/advanced-configurations/data-storage-configuration.md

@@ -164,6 +164,12 @@ Aggregated analytics corresponds to data that is used for the display of charts
 
 #### How To Configure Tyk Pump To Write Aggregated Analytics To A SQL Database?
 
+{{< note success >}}
+**Note** 
+
+SQLite support will be deprecated from Tyk 5.7.0. To avoid disrupution, please transition to PostgreSQL, MongoDB or one of the listed compatible alternatives.
+{{< /note >}}
+
 Storage of aggregated analytics data has been tested with PostgreSQL and SqlLite databases. The following environment variables can be used to manage this configuration:
 
 - *TYK_PMP_PUMPS_SQLAGGREGATE_TYPE*: Set to *sql_aggregate* to configure Pump to store aggregated analytics data for charts and graphs in dashboard to a SQL based database.

tyk-docs/content/product-stack/tyk-dashboard/release-notes/version-5.6.md

@@ -144,7 +144,27 @@ An example is given below for illustrative purposes only. Tested Versions and Co
 
 ### Deprecations
 <!-- Required. Use the following statement if there are no deprecations, or explain if there are -->
-There are no deprecations in this release.
+
+We are deprecating support for SQLite, External OAuth Middleware, and OpenID Connect (OIDC) Middleware in Tyk Dashboard to simplify the platform and enhance overall performance. These changes will take effect from 5.7.0.
+
+### Why the Change?
+
+### SQLite
+
+While useful for testing, SQLite is not designed for production environments. By focusing on PostgreSQL and MongoDB, we can provide users with more scalable and reliable options.
+
+### External OAuth Middleware
+
+This feature serves a similar purpose to our JWT Authentication and may lead to confusion. We recommend transitioning to JWT Authentication for a more streamlined experience.
+
+### OpenID Connect (OIDC) Middleware 
+
+The low adoption of this option, along with its functional overlap with other supported authentication methods, prompts us to deprecate OIDC middleware to reduce complexity within the platform. We recommend users transition to JWT Authentication.
+
+
+We encourage users to switch to the recommended alternatives. For more detailed information, please refer to the [Documentation](https://tyk.io/docs/basic-config-and-security/security/authentication-authorization/openid-connect/) 
+
+
 <!-- Optional section!
 Used to share and notify users about our plan to deprecate features, configs etc.
 Once you put an item in this section, we must keep this item listed in all the following releases till the deprecation happens. -->

tyk-docs/content/product-stack/tyk-enterprise-developer-portal/deploy/install-tyk-enterprise-portal.md

@@ -68,5 +68,12 @@ In terms of admin functionality, the only limitation will be the inability to ap
 
 
 ### Does the portal support SQL databases for storing the portal's CMS assets?
+
+{{< note success >}}
+**Note** 
+
+SQLite support will be deprecated from Tyk 5.7.0. To avoid disrupution, please transition to PostgreSQL, MongoDB or one of the listed compatible alternatives.
+{{< /note >}}
+
 Yes, since 1.4.0 version of the Enterprise Developer Portal, it supports SQL databases (MariaDB, SQLite, MySQL, and PostgreSQL) for storing the portal's CMS assets.
 During the bootstrap process, the portal will create the appropriate tables in the main database. The only thing required to enable SQL storage for the portal's assets is to specify the `db` [storage type]({{< ref "/product-stack/tyk-enterprise-developer-portal/deploy/configuration#portal_storage" >}}) either via a config file or an environment variable.

tyk-docs/content/product-stack/tyk-enterprise-developer-portal/deploy/install-tyk-enterprise-portal/install-portal-using-docker.md

@@ -159,6 +159,12 @@ The above MySQL configuration is an example. You can customize deployment of you
 Please refer to the [MySQL documentation](https://dev.mysql.com/doc/refman/5.7/en/charset-applications.html) for further guidance.
 {{< /warning >}}
 
+{{< note success >}}
+**Note** 
+
+SQLite support will be deprecated from Tyk 5.7.0. To avoid disrupution, please transition to PostgreSQL, MongoDB or one of the listed compatible alternatives.
+{{< /note >}}
+
 #### Create an environment variables file
 Creating an environment variables file to specify settings for the portal is the next step.
 This is optional, as you can alternatively specify all the variables using the -e option when starting your deployment.

tyk-docs/content/product-stack/tyk-enterprise-developer-portal/deploy/install-tyk-enterprise-portal/install-portal-using-helm.md

@@ -42,6 +42,12 @@ Where `TYK_ORG` and `TYK_AUTH` are the Tyk Dashboard Organization ID and the Tyk
 
 ## Config settings
 
+{{< note success >}}
+**Note** 
+
+SQLite support will be deprecated from Tyk 5.7.0. To avoid disrupution, please transition to PostgreSQL, MongoDB or one of the listed compatible alternatives.
+{{< /note >}}
+
 You must set the following values in the `values.yaml` or with `--set {field-name}={field-value}` with the helm upgrade command:
 
 | Field Name | Description |

tyk-docs/content/product-stack/tyk-enterprise-developer-portal/deploy/install-tyk-enterprise-portal/install-portal-using-rpm.md

@@ -48,6 +48,13 @@ sudo rpm -i portal-1.7.0-1.x86_64.rpm
 ### Configure and launch the portal
 
 #### Update the configuration file with your license
+
+{{< note success >}}
+**Note** 
+
+SQLite support will be deprecated from Tyk 5.7.0. To avoid disrupution, please transition to PostgreSQL, MongoDB or one of the listed compatible alternatives.
+{{< /note >}}
+
 Before starting the portal service, you need to configure the portal. Once the rpm package has been installed, the portal configuration file will be located in `/opt/portal/portal.conf`.
 Initially, the config file is filled with the default values. The minimal configuration change to start the portal is to add the `LicenseKey` property to the config file.
 The below sample configuration will start the portal on portal 3001 with SQLite as a database, no TLS enabled, and all CMS assets (images, theme files, etc.) are stored in the filesystem.

tyk-docs/content/tyk-dashboard/database-options.md

@@ -24,6 +24,12 @@ Please check [here]({{< ref "planning-for-production/database-settings/mongodb.m
 
 {{< include "sql-versions-include" >}}
 
+{{< note success >}}
+**Note** 
+
+SQLite support will be deprecated from Tyk 5.7.0. To avoid disrupution, please transition to PostgreSQL, MongoDB or one of the listed compatible alternatives.
+{{< /note >}}
+
 ### Configuring PostgreSQL
 
 Please check [here]({{< ref "planning-for-production/database-settings/postgresql.md" >}}) for production configurations.
@@ -41,3 +47,4 @@ We recommend the following:
 
 * For PoC installations, you can use any of the following platforms (SQLite, PostgreSQL or MongoDB).
 * For production installations, we **only** support MongoDB or PostgreSQL
+

tyk-docs/content/tyk-pump/configuration.md

@@ -28,6 +28,12 @@ The Tyk Dashboard uses the `mongo-pump-aggregate` collection to display analytic
 {{< tab_end >}}
 {{< tab_start "SQL" >}}
 
+{{< note success >}}
+**Note** 
+
+SQLite support will be deprecated from Tyk 5.7.0. To avoid disrupution, please transition to PostgreSQL, MongoDB or one of the listed compatible alternatives.
+{{< /note >}}
+
 In v4.0 of the Tyk Dashboard, we have added support for the following SQL platforms:
 - PostgreSQL
 - SQLite