github-actions[bot] a44db38d05
Version packages (#3345)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2025-01-13 16:32:43 -08:00

20 KiB

@atproto/oauth-provider

0.2.12

Patch Changes

0.2.11

Patch Changes

  • Updated dependencies []:
    • @atproto/common@0.4.6

0.2.10

Patch Changes

  • Updated dependencies [588baae12]:
    • @atproto/common@0.4.5

0.2.9

Patch Changes

0.2.8

Patch Changes

0.2.7

Patch Changes

0.2.6

Patch Changes

0.2.5

Patch Changes

  • Updated dependencies [80450cbf2]:
    • @atproto-labs/fetch-node@0.1.3

0.2.4

Patch Changes

  • Updated dependencies [8943c1008]:
    • @atproto-labs/fetch-node@0.1.2

0.2.3

Patch Changes

0.2.2

Patch Changes

0.2.1

Patch Changes

0.2.0

Minor Changes

  • #2734 dee817b6e Thanks @matthieusieben! - Remove "nonce" from authorization request

  • #2734 dee817b6e Thanks @matthieusieben! - Mandate the use of "atproto" scope

  • #2734 dee817b6e Thanks @matthieusieben! - Remove "openid" compatibility. The reason is that although we were technically "openid" compatible, ATProto identifiers are distributed identifiers. When a client relies on OpenID to authenticate users, it will use the auth provider in combination with the identifier to uniquely identify the user. Since ATProto identifiers are meant to be able to move from one provider to the other, OpenID compatibility could break authentication after a user was migrated to a different provider.

    The way OpenID compliant clients would adapt to this particularity would typically be to remove the provider + identifier combination and use the identifier alone. While this is indeed the right way to handle ATProto identifiers, it requires more work to avoid impersonation. In particular, when obtaining a user identifier, the client must verify that the issuer of the identity token is indeed the server responsible for that user. This mechanism being not enforced by the OpenID standard, OpenID compatibility could lead to security issues. For this reason, we decided to remove OpenID compatibility from the OAuth provider.

    Note that a trusted central authority could still offer OpenID compatibility by relying on ATProto's regular OAuth flow under the hood. This capability is out of the scope of this library.

Patch Changes

0.1.3

Patch Changes

  • #2729 35a126429 Thanks @matthieusieben! - The non-standard introspection_endpoint_auth_method, and introspection_endpoint_auth_signing_alg client metadata properties were removed. The client's token_endpoint_auth_method, and token_endpoint_auth_signing_alg properties are now used as the only indication of how a client must authenticate at the introspection endpoint.

  • #2729 35a126429 Thanks @matthieusieben! - The non-standard revocation_endpoint_auth_method, and revocation_endpoint_auth_signing_alg client metadata properties were removed. The client's token_endpoint_auth_method, and token_endpoint_auth_signing_alg properties are now used as the only indication of how a client must authenticate at the revocation endpoint.

  • #2729 35a126429 Thanks @matthieusieben! - The non-standard pushed_authorization_request_endpoint_auth_method, and pushed_authorization_request_endpoint_auth_signing_alg client metadata properties were removed. The client's token_endpoint_auth_method, and token_endpoint_auth_signing_alg properties are now used as the only indication of how a client must authenticate at the introspection endpoint.

  • #2728 5131b027f Thanks @matthieusieben! - Allow charset in content-type header of incoming requests

  • #2727 3ebcd4e61 Thanks @matthieusieben! - Do not require "exp" claim in dpop proof

  • Updated dependencies [35a126429]:

    • @atproto/oauth-types@0.1.3

0.1.2

Patch Changes

0.1.1

Patch Changes

0.1.0

Minor Changes

Patch Changes

  • Updated dependencies [a8d6c1123]:
    • @atproto-labs/simple-store-memory@0.1.0
    • @atproto-labs/simple-store@0.1.0
    • @atproto-labs/fetch-node@0.1.0
    • @atproto/oauth-types@0.1.0
    • @atproto-labs/fetch@0.1.0
    • @atproto/jwk-jose@0.1.0
    • @atproto-labs/pipe@0.1.0
    • @atproto/jwk@0.1.0