Skip to content

Latest commit

 

History

History
1709 lines (1238 loc) · 47 KB

CHANGELOG.md

File metadata and controls

1709 lines (1238 loc) · 47 KB

@backstage/plugin-auth-node

0.6.1-next.0

Patch Changes

0.6.0

Minor Changes

  • 61f464e: Added auth.providers.<providerId>.sessionDuration config for auth providers to allow the lifespan of user sessions to be configured.

Patch Changes

0.6.0-next.2

Patch Changes

0.6.0-next.1

Minor Changes

  • 61f464e: Added auth.providers.<providerId>.sessionDuration config for auth providers to allow the lifespan of user sessions to be configured.

Patch Changes

0.5.7-next.0

Patch Changes

0.5.6

Patch Changes

0.5.6-next.1

Patch Changes

0.5.6-next.0

Patch Changes

0.5.5

Patch Changes

0.5.5-next.2

Patch Changes

0.5.5-next.1

Patch Changes

0.5.5-next.0

Patch Changes

0.5.4

Patch Changes

  • a0a9a4a: Browsers silently drop cookies that exceed 4KB, which can be problematic for refresh tokens and other large cookies.This update ensures that large cookies, like refresh tokens, are not dropped by browsers, maintaining the integrity of the authentication process. The changes include both the implementation of the cookie splitting logic and corresponding tests to validate the new functionality.
  • 4e58bc7: Upgrade to uuid v11 internally
  • Updated dependencies

0.5.4-next.2

Patch Changes

0.5.4-next.1

Patch Changes

0.5.4-next.0

Patch Changes

  • a0a9a4a: Browsers silently drop cookies that exceed 4KB, which can be problematic for refresh tokens and other large cookies.This update ensures that large cookies, like refresh tokens, are not dropped by browsers, maintaining the integrity of the authentication process. The changes include both the implementation of the cookie splitting logic and corresponding tests to validate the new functionality.
  • Updated dependencies

0.5.3

Patch Changes

  • 217458a: Added a new allowedDomains option for the common emailLocalPartMatchingUserEntityName sign-in resolver.
  • 094eaa3: Remove references to in-repo backend-common
  • e4ad29a: Fix authentication error handling using redirect flow via enableExperimentalRedirectFlow config. If an error is caught during authentication, the user is redirected back to app origin with error query parameter containing the error message.
  • Updated dependencies

0.5.3-next.1

Patch Changes

0.5.3-next.0

Patch Changes

0.5.2

Patch Changes

0.5.2-next.2

Patch Changes

0.5.2-next.1

Patch Changes

0.5.2-next.0

Patch Changes

0.5.0

Minor Changes

  • 579afd0: BREAKING: Sign-in resolvers configured via .signIn.resolvers now take precedence over sign-in resolvers passed to signInResolver option of createOAuthProviderFactory. This effectively makes sign-in resolvers passed via the signInResolver the default one, which you can then override through configuration.

Patch Changes

0.5.0-next.3

Patch Changes

0.5.0-next.2

Minor Changes

  • 579afd0: BREAKING: Sign-in resolvers configured via .signIn.resolvers now take precedence over sign-in resolvers passed to signInResolver option of createOAuthProviderFactory. This effectively makes sign-in resolvers passed via the signInResolver the default one, which you can then override through configuration.

Patch Changes

0.4.18-next.1

Patch Changes

0.4.18-next.0

Patch Changes

0.4.17

Patch Changes

0.4.17-next.1

Patch Changes

0.4.16-next.0

Patch Changes

0.4.14

Patch Changes

  • 798ec37: Updated scope management for OAuth providers, where the createOAuthAuthenticator now accepts a new collection of scopes options:

    • scopes.persist - Whether scopes should be persisted, replaces the shouldPersistScopes option.
    • scopes.required - A list of required scopes that will always be requested.
    • scopes.transform - A function that can be used to transform the scopes before they are requested.

    The createOAuthProviderFactory has also received a new additionalScopes option, and will also read additionalScopes from the auth provider configuration. Both of these can be used to add additional scopes that should always be requested.

    A significant change under the hood that this new scope management brings is that providers that persist scopes will now always merge the already granted scopes with the requested ones. The previous behavior was that the full authorization flow would not include existing scopes, while the refresh flow would only include the existing scopes.

  • d44a20a: Added additional plugin metadata to package.json.

  • Updated dependencies

0.4.14-next.3

Patch Changes

  • 798ec37: Updated scope management for OAuth providers, where the createOAuthAuthenticator now accepts a new collection of scopes options:

    • scopes.persist - Whether scopes should be persisted, replaces the shouldPersistScopes option.
    • scopes.required - A list of required scopes that will always be requested.
    • scopes.transform - A function that can be used to transform the scopes before they are requested.

    The createOAuthProviderFactory has also received a new additionalScopes option, and will also read additionalScopes from the auth provider configuration. Both of these can be used to add additional scopes that should always be requested.

    A significant change under the hood that this new scope management brings is that providers that persist scopes will now always merge the already granted scopes with the requested ones. The previous behavior was that the full authorization flow would not include existing scopes, while the refresh flow would only include the existing scopes.

  • d44a20a: Added additional plugin metadata to package.json.

  • Updated dependencies

0.4.14-next.2

Patch Changes

0.4.14-next.1

Patch Changes

0.4.14-next.0

Patch Changes

0.4.13

Patch Changes

0.4.13-next.1

Patch Changes

0.4.13-next.0

Patch Changes

0.4.12

Patch Changes

0.4.12-next.1

Patch Changes

0.4.12-next.0

Patch Changes

0.4.11

Patch Changes

0.4.10

Patch Changes

0.4.9

Patch Changes

  • b4fc6e3: Deprecated the getBearerTokenFromAuthorizationHeader function, which is being replaced by the new HttpAuthService.
  • 2af5354: Bump dependency jose to v5
  • 0fb419b: Updated dependency uuid to ^9.0.0. Updated dependency @types/uuid to ^9.0.0.
  • b1b012d: Fix issue with providerInfo not being set properly for some proxy providers, by making providerInfo an explicit optional return from authenticate
  • Updated dependencies

0.4.9-next.2

Patch Changes

0.4.9-next.1

Patch Changes

0.4.8-next.0

Patch Changes

  • b4fc6e3: Deprecated the getBearerTokenFromAuthorizationHeader function, which is being replaced by the new HttpAuthService.
  • 2af5354: Bump dependency jose to v5
  • 0fb419b: Updated dependency uuid to ^9.0.0. Updated dependency @types/uuid to ^9.0.0.
  • b1b012d: Fix issue with providerInfo not being set properly for some proxy providers, by making providerInfo an explicit optional return from authenticate
  • Updated dependencies

0.4.4

Patch Changes

0.4.4-next.3

Patch Changes

0.4.4-next.2

Patch Changes

0.4.4-next.1

Patch Changes

0.4.4-next.0

Patch Changes

0.4.3

Patch Changes

0.4.3-next.2

Patch Changes

0.4.3-next.1

Patch Changes

0.4.3-next.0

Patch Changes

0.4.2

Patch Changes

0.4.2-next.3

Patch Changes

0.4.2-next.2

Patch Changes

0.4.2-next.1

Patch Changes

0.4.2-next.0

Patch Changes

0.4.1

Patch Changes

0.4.1-next.2

Patch Changes

0.4.1-next.1

Patch Changes

0.4.1-next.0

Patch Changes

0.4.0

Minor Changes

  • 6f142d5356: BREAKING: The recently introduced ProxyAuthenticator.initialize() method is no longer async to match the way the OAuth equivalent is implemented.

Patch Changes

0.4.0-next.2

Minor Changes

  • 6f142d5356: BREAKING: The recently introduced ProxyAuthenticator.initialize() method is no longer async to match the way the OAuth equivalent is implemented.

Patch Changes

0.3.2-next.1

Patch Changes

0.3.2-next.0

Patch Changes

0.3.0

Minor Changes

  • 8513cd7d00e3: Introduced a new system for building auth providers for @backstage/plugin-auth-backend, which both increases the amount of code re-use across providers, and also works better with the new backend system.

    Many existing types have been moved from @backstage/plugin-auth-backend in order to avoid a direct dependency on the plugin from modules.

    Auth provider integrations are now primarily implemented through a pattern of creating "authenticators", which are in turn specific to each kind of integrations. Initially there are two types: createOAuthAuthenticator and createProxyAuthenticator. These come paired with functions that let you create the corresponding route handlers, createOAuthRouteHandlers and createProxyAuthRouteHandlers, as well as provider factories, createOAuthProviderFactory and createProxyAuthProviderFactory. This new authenticator pattern allows the sign-in logic to be separated from the auth integration logic, allowing it to be completely re-used across all providers of the same kind.

    The new provider factories also implement a new declarative way to configure sign-in resolvers, rather than configuration through code. Sign-in resolvers can now be configured through the resolvers configuration key, where the first resolver that provides an identity will be used, for example:

    auth:
  providers:
    google:
      development:
        clientId: ...
        clientSecret: ...
        signIn:
          resolvers:
            - resolver: emailMatchingUserEntityAnnotation
            - resolver: emailLocalPartMatchingUserEntityName

    These configurable resolvers are created with a new createSignInResolverFactory function, which creates a sign-in resolver factory, optionally with an options schema that will be used both when configuring the sign-in resolver through configuration and code.

    The internal helpers from @backstage/plugin-auth-backend that were used to implement auth providers using passport strategies have now also been made available as public API, through PassportHelpers and PassportOAuthAuthenticatorHelper.

Patch Changes

0.3.0-next.3

Patch Changes

0.3.0-next.2

Patch Changes

0.3.0-next.1

Patch Changes

0.3.0-next.0

Minor Changes

  • 8513cd7d00e3: Introduced a new system for building auth providers for @backstage/plugin-auth-backend, which both increases the amount of code re-use across providers, and also works better with the new backend system.

    Many existing types have been moved from @backstage/plugin-auth-backend in order to avoid a direct dependency on the plugin from modules.

    Auth provider integrations are now primarily implemented through a pattern of creating "authenticators", which are in turn specific to each kind of integrations. Initially there are two types: createOAuthAuthenticator and createProxyAuthenticator. These come paired with functions that let you create the corresponding route handlers, createOAuthRouteHandlers and createProxyAuthRouteHandlers, as well as provider factories, createOAuthProviderFactory and createProxyAuthProviderFactory. This new authenticator pattern allows the sign-in logic to be separated from the auth integration logic, allowing it to be completely re-used across all providers of the same kind.

    The new provider factories also implement a new declarative way to configure sign-in resolvers, rather than configuration through code. Sign-in resolvers can now be configured through the resolvers configuration key, where the first resolver that provides an identity will be used, for example:

    auth:
  providers:
    google:
      development:
        clientId: ...
        clientSecret: ...
        signIn:
          resolvers:
            - resolver: emailMatchingUserEntityAnnotation
            - resolver: emailLocalPartMatchingUserEntityName

    These configurable resolvers are created with a new createSignInResolverFactory function, which creates a sign-in resolver factory, optionally with an options schema that will be used both when configuring the sign-in resolver through configuration and code.

    The internal helpers from @backstage/plugin-auth-backend that were used to implement auth providers using passport strategies have now also been made available as public API, through PassportHelpers and PassportOAuthAuthenticatorHelper.

Patch Changes

0.2.17

Patch Changes

0.2.17-next.2

Patch Changes

0.2.17-next.1

Patch Changes

0.2.17-next.0

Patch Changes

0.2.16

Patch Changes

0.2.16-next.0

Patch Changes

0.2.15

Patch Changes

0.2.15-next.2

Patch Changes

0.2.15-next.1

Patch Changes

0.2.15-next.0

Patch Changes

0.2.14

Patch Changes

0.2.14-next.1

Patch Changes

0.2.14-next.0

Patch Changes

0.2.13

Patch Changes

0.2.13-next.2

Patch Changes

0.2.13-next.1

Patch Changes

0.2.13-next.0

Patch Changes

0.2.12

Patch Changes

0.2.12-next.2

Patch Changes

0.2.12-next.1

Patch Changes

0.2.12-next.0

Patch Changes

0.2.11

Patch Changes

0.2.11-next.2

Patch Changes

0.2.11-next.1

Patch Changes

0.2.11-next.0

Patch Changes

0.2.9

Patch Changes

0.2.9-next.1

Patch Changes

0.2.9-next.0

Patch Changes

0.2.8

Patch Changes

0.2.8-next.3

Patch Changes

0.2.8-next.2

Patch Changes

0.2.8-next.1

Patch Changes

0.2.8-next.0

Patch Changes

0.2.7

Patch Changes

0.2.7-next.1

Patch Changes

0.2.7-next.0

Patch Changes

0.2.6

Patch Changes

0.2.6-next.2

Patch Changes

0.2.6-next.1

Patch Changes

0.2.6-next.0

Patch Changes

0.2.5

Patch Changes

  • 9212439d15: Minor update to tests
  • 2cbd533426: IdentityClient is now deprecated. Please migrate to IdentityApi and DefaultIdentityClient instead. The authenticate function on DefaultIdentityClient is also deprecated. Please use getIdentity instead.
  • 667d917488: Updated dependency msw to ^0.47.0.
  • 87ec2ba4d6: Updated dependency msw to ^0.46.0.
  • bf5e9030eb: Updated dependency msw to ^0.45.0.
  • Updated dependencies

0.2.5-next.3

Patch Changes

0.2.5-next.2

Patch Changes

  • 2cbd533426: IdentityClient is now deprecated. Please migrate to IdentityApi and DefaultIdentityClient instead. The authenticate function on DefaultIdentityClient is also deprecated. Please use getIdentity instead.
  • 667d917488: Updated dependency msw to ^0.47.0.
  • 87ec2ba4d6: Updated dependency msw to ^0.46.0.
  • Updated dependencies

0.2.5-next.1

Patch Changes

0.2.5-next.0

Patch Changes

  • bf5e9030eb: Updated dependency msw to ^0.45.0.
  • Updated dependencies

0.2.4

Patch Changes

0.2.4-next.0

Patch Changes

0.2.3

Patch Changes

0.2.3-next.2

Patch Changes

  • a70869e775: Updated dependency msw to ^0.43.0.
  • Updated dependencies

0.2.3-next.1

Patch Changes

0.2.3-next.0

Patch Changes

0.2.2

Patch Changes

  • 5ca0b86b88: Address corner cases where the key store was not being created at startup
  • 8f7b1835df: Updated dependency msw to ^0.41.0.
  • 9079a78078: Added configurable algorithms array for IdentityClient
  • Updated dependencies

0.2.2-next.2

Patch Changes

0.2.2-next.1

Patch Changes

  • 8f7b1835df: Updated dependency msw to ^0.41.0.
  • Updated dependencies

0.2.2-next.0

Patch Changes

  • 9079a78078: Added configurable algorithms array for IdentityClient
  • Updated dependencies

0.2.1

Patch Changes

0.2.1-next.1

Patch Changes

0.2.1-next.0

Patch Changes

0.2.0

Minor Changes

  • 15d3a3c39a: BREAKING: Removed the deprecated id and entity fields from BackstageSignInResult.

Patch Changes

0.2.0-next.0

Minor Changes

  • 15d3a3c39a: BREAKING: Removed the deprecated id and entity fields from BackstageSignInResult.

Patch Changes

0.1.6

Patch Changes

0.1.5

Patch Changes

0.1.5-next.0

Patch Changes

0.1.4

Patch Changes

0.1.3

Patch Changes

0.1.2

Patch Changes

0.1.1

Patch Changes

0.1.0

Minor Changes

  • 9058bb1b5e: Added this package, to hold shared types and functionality that other backend packages need to import.

Patch Changes