|
| 1 | +--- |
| 2 | +title: "Duende IdentityServer v7.2 to v7.3" |
| 3 | +sidebar: |
| 4 | + order: 27 |
| 5 | + label: v7.2 → v7.3 |
| 6 | +--- |
| 7 | + |
| 8 | +This upgrade guide covers upgrading from Duende IdentityServer v7.2 to v7.3 ([release notes](https://github.com/DuendeSoftware/products/releases/tag/is-7.3.0)). |
| 9 | + |
| 10 | +IdentityServer 7.3.0 is a significant release that includes: |
| 11 | + |
| 12 | +- [FAPI 2.0 Security Profile](https://openid.net/specs/fapi-security-profile-2_0-final.html) certification |
| 13 | +- JWT Response from the introspection endpoint ([RFC 9701](https://www.rfc-editor.org/rfc/rfc9701.html)) |
| 14 | +- Diagnostic data |
| 15 | +- Removal of the experimental label from OpenTelemetry metrics |
| 16 | +- Additional license compliance warnings |
| 17 | +- Several bug fixes |
| 18 | +- Numerous small code quality and performance enhancements from the community |
| 19 | + |
| 20 | +There are no schema changes needed for IdentityServer 7.3. Small code changes maybe be required for some users to upgrade: |
| 21 | + |
| 22 | +- The `SendLogoutNotificationAsync` method has been removed from the `DefaultBackChannelLogoutService` class |
| 23 | +- Client `Secret` is now required for Clients with `ClientCredentials` grant |
| 24 | + |
| 25 | +## Step 1: Update NuGet package |
| 26 | + |
| 27 | +In your IdentityServer host project, update the version of the NuGet. |
| 28 | +For example in your project file: |
| 29 | + |
| 30 | +```xml |
| 31 | +<PackageReference Include="Duende.IdentityServer" Version="7.2.0" /> |
| 32 | +``` |
| 33 | + |
| 34 | +would change to: |
| 35 | + |
| 36 | +```xml |
| 37 | +<PackageReference Include="Duende.IdentityServer" Version="7.3.0" /> |
| 38 | +``` |
| 39 | + |
| 40 | +## Step 2: Breaking Changes |
| 41 | + |
| 42 | +Small code changes maybe be required for some users to upgrade. |
| 43 | + |
| 44 | +#### The `SendLogoutNotificationAsync` Method Has Been Removed From The `DefaultBackChannelLogoutService` Class |
| 45 | + |
| 46 | +To fix a bug where when using Entity Framework Core, code which previously executed in parallel needed to be modified to execute sequentially. |
| 47 | +This required the removal of the `SendLogoutNotificationAsync` method in the `DefaultBackChannelLogoutService` class. |
| 48 | + |
| 49 | +If you have previously overridden the `SendLogoutNotificationAsync` as an extensibility point, you will likely need to move your customization to the `PostLogoutJwt` method. |
| 50 | + |
| 51 | +https://github.com/DuendeSoftware/products/pull/2019 |
| 52 | + |
| 53 | +#### Client `Secret` Is Now Required For Clients With `ClientCredentials` Grant |
| 54 | + |
| 55 | +Previously, it was possible to configure a client to allow the `ClientCredentials` grant without requiring a client secret, which is undesirable. |
| 56 | +The default validation of clients has been updated to ensure any client which allows the `ClientCredentials` grant also sets the `RequireClientSecret` flag to `true`, |
| 57 | +to disallow the configuration of a private client to behave like a public client. |
| 58 | + |
| 59 | +https://github.com/DuendeSoftware/products/pull/1796 |
| 60 | + |
| 61 | +#### Removal Of The Experimental Label From OpenTelemetry Metrics |
| 62 | + |
| 63 | +Several [OpenTelemetry metrics](/identityserver/diagnostics/otel.md#detailed-metrics) previously created by the meter named |
| 64 | +"Duende.IdentityServer.Experimental" have been moved to the "Duende.IdentityServer" meter. |
| 65 | + |
| 66 | +## Step 3: Done! |
| 67 | + |
| 68 | +That's it. Of course, at this point you can and should test that your IdentityServer is updated and working properly. |
0 commit comments