Update GitHub links to 'products' repository

Replaced outdated links pointing to 'IdentityServer' repository with updated links to the 'products' repository.

Author: khalidabuhakmeh

src/content/docs/identityserver/upgrades/is4-v4-to-dis-v6.md

@@ -16,7 +16,7 @@ This upgrade guide covers upgrading from IdentityServer4 v4.1.x to Duende Identi
 
 :::note
 With any major release, there is always the possibility of some breaking changes.
-[This issue tracks](https://github.com/DuendeSoftware/IdentityServer/issues/351) the list of updates where a breaking change might affect your use of IdentityServer. It would be useful to review it to understand if any of these changes affect you.
+[This issue tracks](https://github.com/DuendeSoftware/products/issues/351) the list of updates where a breaking change might affect your use of IdentityServer. It would be useful to review it to understand if any of these changes affect you.
 :::
 
 ## Step 1: Update to .NET 6
@@ -83,10 +83,10 @@ These include:
 
 * A new `Keys` table for the automatic key management feature in the operational database.
 * A new `RequireResourceIndicator` boolean column on the `ApiResources` table in the configuration database.
-* A new index on the `ConsumedTime` column in the `PersistedGrants` table ([more details](https://github.com/DuendeSoftware/IdentityServer/pull/84)).
-* A new table called `IdentityProviders` for storing the OIDC provider details ([more details](https://github.com/DuendeSoftware/IdentityServer/pull/188)).
-* Add missing columns for created, updated, etc. to EF entities ([more details](https://github.com/DuendeSoftware/IdentityServer/pull/356)).
-* Add unique constraints to EF tables where duplicate records not allowed ([more details](https://github.com/DuendeSoftware/IdentityServer/pull/355)).
+* A new index on the `ConsumedTime` column in the `PersistedGrants` table ([more details](https://github.com/DuendeSoftware/products/pull/84)).
+* A new table called `IdentityProviders` for storing the OIDC provider details ([more details](https://github.com/DuendeSoftware/products/pull/188)).
+* Add missing columns for created, updated, etc. to EF entities ([more details](https://github.com/DuendeSoftware/products/pull/356)).
+* Add unique constraints to EF tables where duplicate records not allowed ([more details](https://github.com/DuendeSoftware/products/pull/355)).
 
 IdentityServer is abstracted from the data store on multiple levels, so the exact steps involved in updating your data store will depend on your implementation details. 
 

src/content/docs/identityserver/upgrades/v5_0-to-v5_1.md

@@ -31,7 +31,7 @@ would change to:
 If you are using the `Duende.IdentityServer.EntityFramework` package as the implementation for the database for your operational data, then there is a small database schema update.
 This includes:
 
-* A new index on the `ConsumedTime` column in the `PersistedGrants` table ([more details](https://github.com/DuendeSoftware/IdentityServer/pull/84)).
+* A new index on the `ConsumedTime` column in the `PersistedGrants` table ([more details](https://github.com/DuendeSoftware/products/pull/84)).
 
 If you're using EntityFramework Core migrations as the mechanism for managing schema changes over time, the commands below will update those migrations with the new changes.
 Note that you might need to adjust based on your specific organization of the migration files.

src/content/docs/identityserver/upgrades/v5_1-to-v5_2.md

@@ -28,7 +28,7 @@ would change to:
 
 ## Step 2: Update Database Schema (if needed)
 
-If you are using a [database](/identityserver/data) for your configuration data, then there is a database schema update for the new *Dynamic Providers* feature ([more details](https://github.com/DuendeSoftware/IdentityServer/pull/188)).
+If you are using a [database](/identityserver/data) for your configuration data, then there is a database schema update for the new *Dynamic Providers* feature ([more details](https://github.com/DuendeSoftware/products/pull/188)).
 This includes:
 
 * A new table called `IdentityProviders` for storing the OIDC provider details. Its TSQL schema would look like this:
@@ -69,7 +69,7 @@ Some organizations prefer to use other tools for managing schema changes. You're
 ## Step 4: Update custom AuthorizeInteractionResponseGenerator (if needed)
 
 If you have created a custom, derived implementation of the `AuthorizeInteractionResponseGenerator`, then the constructor must accept an additional parameter of type `IdentityServerOptions`.
-This is needed for the new [tenant validation](https://github.com/DuendeSoftware/IdentityServer/pull/197) in authorize endpoint requests.
+This is needed for the new [tenant validation](https://github.com/DuendeSoftware/products/pull/197) in authorize endpoint requests.
 
 ## Step 5: Done!
 

src/content/docs/identityserver/upgrades/v5_2-to-v6_0.md

@@ -14,7 +14,7 @@ The most significant aspect of this upgrade is that Duende IdentityServer v6.0 t
 
 :::note
 With any major release, there is always the possibility of some breaking changes.
-[This issue tracks](https://github.com/DuendeSoftware/IdentityServer/issues/351) the list of updates where a breaking change might affect your use of IdentityServer. It would be useful to review it to understand if any of these changes affect you.
+[This issue tracks](https://github.com/DuendeSoftware/products/issues/351) the list of updates where a breaking change might affect your use of IdentityServer. It would be useful to review it to understand if any of these changes affect you.
 :::
 
 ## Step 1: Update to .NET 6
@@ -57,8 +57,8 @@ would change to:
 If you are using a [database](/identityserver/data) for your configuration data, then there is a small database schema update.
 This includes:
 
-* Add missing columns for created, updated, etc. to EF entities ([more details](https://github.com/DuendeSoftware/IdentityServer/pull/356)).
-* Add unique constraints to EF tables where duplicate records not allowed ([more details](https://github.com/DuendeSoftware/IdentityServer/pull/355)).
+* Add missing columns for created, updated, etc. to EF entities ([more details](https://github.com/DuendeSoftware/products/pull/356)).
+* Add unique constraints to EF tables where duplicate records not allowed ([more details](https://github.com/DuendeSoftware/products/pull/355)).
 IdentityServer is abstracted from the data store on multiple levels, so the exact steps involved in updating your data store will depend on your implementation details. 
 
 #### Custom Store Implementations

src/content/docs/identityserver/upgrades/v6_0-to-v6_1.md

@@ -31,9 +31,9 @@ would change to:
 If you are using a [database](/identityserver/data) for your configuration or operational data, then there is a database schema update.
 This includes:
 
-* Server-side sessions feature, which requires a new table ([more details](https://github.com/DuendeSoftware/IdentityServer/pull/743)).
-* Session coordination feature, which adds a column to the Clients table ([more details](https://github.com/DuendeSoftware/IdentityServer/pull/820)).
-* Improve primary key on the persisted grants table ([more details](https://github.com/DuendeSoftware/IdentityServer/pull/793)).
+* Server-side sessions feature, which requires a new table ([more details](https://github.com/DuendeSoftware/products/pull/743)).
+* Session coordination feature, which adds a column to the Clients table ([more details](https://github.com/DuendeSoftware/products/pull/820)).
+* Improve primary key on the persisted grants table ([more details](https://github.com/DuendeSoftware/products/pull/793)).
 
 IdentityServer is abstracted from the data store on multiple levels, so the exact steps involved in updating your data store will depend on your implementation details. 
 

src/content/docs/identityserver/upgrades/v6_2-to-v6_3.md

@@ -87,19 +87,19 @@ IdentityServer depends on ASP.NET Data Protection. Data Protection encrypts and
   - Register the derived class as an implementation of `ITokenCleanupService`, and
   - Remove the `IServerSideSessionsMarker` from any calls to the base constructor.
 
-  See issue [#981](https://github.com/DuendeSoftware/IdentityServer/issues/981).
+  See issue [#981](https://github.com/DuendeSoftware/products/issues/981).
 
 - The `TokenCleanupService.RemoveExpiredGrantsAsync` method was renamed to `CleanupGrantsAsync` to reflect that it performs all grant cleanup work, including removing consumed grants and expired device codes in addition to expired grants. In the strictest sense, this is a  breaking change, but it is very unlikely to cause issues during an upgrade because even though `RemoveExpiredGrantsAsync` was public, it was not virtual. If you were using `RemoveExpiredGrantsAsync` elsewhere, update your code to use the new name.
 
-  See issue [#981](https://github.com/DuendeSoftware/IdentityServer/issues/981).
+  See issue [#981](https://github.com/DuendeSoftware/products/issues/981).
 
 - The value of the `typ` claim in the header of Logout tokens has changed to `logout+jwt`, which complies with OpenID Connect Back-Channel Logout 1.0. Clients that were previously validating the `typ` need to be updated, or the old `typ` can continue to be used via the new `LogoutTokenJwtType` configuration option.
 
-  See issue [#1169](https://github.com/DuendeSoftware/IdentityServer/issues/1169).
+  See issue [#1169](https://github.com/DuendeSoftware/products/issues/1169).
 
 - The `TokenResponseGenerator.ProcessTokenRequestAsync` virtual method, which generates access and refresh tokens and adds them to a response object, is now called by all token flows except the refresh token flow. This unifies the programming and extensibility model of the generator, which previously had duplicated code in some flows. If you have overridden this virtual method, be aware that it will now be called in all flows. Previously, the authorization code flow, device code flow, and CIBA flow did not invoke this method.
 
-  See pull request: [#1178](https://github.com/DuendeSoftware/IdentityServer/pull/1178).
+  See pull request: [#1178](https://github.com/DuendeSoftware/products/pull/1178).
 
 - One time use (rotated) refresh tokens are now deleted immediately when they are used by default. If you rely on the existing behavior of marking refresh tokens as consumed (perhaps to allow for lenient rotations or replay detection), set the new `PersistentGrantOptions.DeleteOneTimeOnlyRefreshTokensOnUse` option to false.