🤖 Bip Bop - Fusion Framework Release

packages/react/legacy-interopt/CHANGELOG.md

@@ -1,5 +1,18 @@
 # Change Log
 
+## 17.0.1
+
+### Patch Changes
+
+-   [#2524](https://github.com/equinor/fusion-framework/pull/2524) [`1941b76`](https://github.com/equinor/fusion-framework/commit/1941b76bdad85af3fe2ccfa9e46180e14940d2a1) Thanks [@odinr](https://github.com/odinr)! - Fixed `LegacyAuthContainer.registerAppAsync` to not create duplicate AuthApps when additional resources are added to the app.
+
+-   [#2524](https://github.com/equinor/fusion-framework/pull/2524) [`1941b76`](https://github.com/equinor/fusion-framework/commit/1941b76bdad85af3fe2ccfa9e46180e14940d2a1) Thanks [@odinr](https://github.com/odinr)! - Fixed `createServiceResolver` to extract app client id from each services.
+    Previously we assumed that all services registered to the legacy auth container would use the same scope as all other services. This is not the case, as each service can have its own scope. This change allows us to extract the client id from the service definition, which is then used to create the service resolver.
+
+    Resources are indexed by the client id, so when acquiring a resource, the legacy auth container will use the client id to generate an auth token. This token is then used to authenticate the request to the resource.
+
+    **NOTE:** This will and should be deprecated in the future! This "bug" was discovered while an application used a mixed of legacy and new Framework, which caused the application to fail to authenticate requests to the resource (wrong audience).
+
 ## 17.0.0
 
 ### Patch Changes

packages/react/legacy-interopt/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@equinor/fusion-framework-legacy-interopt",
-    "version": "17.0.0",
+    "version": "17.0.1",
     "description": "Library for interopt legacy fusion applications",
     "main": "dist/esm/index.js",
     "exports": {