@backstage/plugin-auth-backend 0.4.9 → 0.5.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,57 @@
1
1
  # @backstage/plugin-auth-backend
2
2
 
3
+ ## 0.5.2
4
+
5
+ ### Patch Changes
6
+
7
+ - 24a67e3e2e: Fixed the fallback identity population to correctly generate an entity reference for `userEntityRef` if no token is provided.
8
+ - Updated dependencies
9
+ - @backstage/backend-common@0.10.0
10
+ - @backstage/test-utils@0.2.0
11
+ - @backstage/catalog-client@0.5.3
12
+
13
+ ## 0.5.1
14
+
15
+ ### Patch Changes
16
+
17
+ - 699c2e9ddc: export minimal typescript types for OIDC provider
18
+ - Updated dependencies
19
+ - @backstage/backend-common@0.9.14
20
+ - @backstage/catalog-model@0.9.8
21
+
22
+ ## 0.5.0
23
+
24
+ ### Minor Changes
25
+
26
+ - a036b65c2f: **BREAKING CHANGE** The `idToken` field of `BackstageIdentity` has been removed, with the `token` taking its place. This means you may need to update existing `signIn.resolver` implementations to return an `token` rather than an `idToken`. This also applies to custom auth providers.
27
+
28
+ The `BackstageIdentity` type has been deprecated and will be removed in the future. Taking its place is the new `BackstageSignInResult` type with the same shape.
29
+
30
+ This change also introduces the new `BackstageIdentityResponse` that mirrors the type with the same name from `@backstage/core-plugin-api`. The `BackstageIdentityResponse` type is different from the `BackstageSignInResult` in that it also has a `identity` field which is of type `BackstageUserIdentity` and is a decoded version of the information within the token.
31
+
32
+ When implementing a custom auth provider that is not based on the `OAuthAdapter` you may need to convert `BackstageSignInResult` into a `BackstageIdentityResponse`, this can be done using the new `prepareBackstageIdentityResponse` function.
33
+
34
+ ### Patch Changes
35
+
36
+ - 8f461e6043: Fixes potential bug introduced in `0.4.10` which causes `OAuth2AuthProvider` to authenticate using credentials in both POST payload and headers.
37
+ This might break some stricter OAuth2 implementations so there is now a `includeBasicAuth` config option that can manually be set to `true` to enable this behavior.
38
+ - dcd1a0c3f4: Minor improvement to the API reports, by not unpacking arguments directly
39
+ - Updated dependencies
40
+ - @backstage/test-utils@0.1.24
41
+ - @backstage/backend-common@0.9.13
42
+
43
+ ## 0.4.10
44
+
45
+ ### Patch Changes
46
+
47
+ - 4bf4111902: Migrated the SAML provider to implement the `authHandler` and `signIn.resolver` options.
48
+ - b055a6addc: Align on usage of `cross-fetch` vs `node-fetch` in frontend vs backend packages, and remove some unnecessary imports of either one of them
49
+ - 36fa32216f: Added signIn and authHandler resolver for oidc provider
50
+ - 7071dce02d: Expose catalog lib in plugin-auth-backend, i.e `CatalogIdentityClient` class is exposed now.
51
+ - 1b69ed44f2: Added custom OAuth2.0 authorization header for generic oauth2 provider.
52
+ - Updated dependencies
53
+ - @backstage/backend-common@0.9.12
54
+
3
55
  ## 0.4.9
4
56
 
5
57
  ### Patch Changes