Version Packages - #50
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@seamless-auth/types@0.15.0
Minor Changes
0857223: Let a deployment refuse synced passkeys and restrict authenticator models.
AuthenticatorPolicySchemagains three fields:syncedPasskeys,alloworblock, defaulting toblockaaguidAllowList, empty by defaultaaguidDenyList, empty by defaultsyncedPasskeysdefaults toblock, which is a behaviour change. Amulti-device credential is synced by a platform password manager, so its private
key exists somewhere outside the authenticator that created it. That is what a
consumer wants and what an organisation issuing its own authenticators does not,
and this package now takes the stricter position by default. A deployment that
wants platform passkeys sets
syncedPasskeys: 'allow'.The judgement is made on backup eligibility rather than current backup state: a
credential that can leave the device is the exposure, whether or not it
already has.
The AAGUID lists restrict which authenticator models may register. They need
attestation: 'direct'to mean anything, because an authenticator that was neverasked to identify itself reports no usable AAGUID.
The whole-object default for
authenticator_policyis now derived from the fielddefaults rather than restated alongside them, so the two cannot drift.