Version Packages - #55
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
1 participant
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.17.0
Minor Changes
b5b056b: Add
max_concurrent_sessionsto the system configuration.How many sessions one user may hold at once.
nullmeans no limit, and that isthe default, so a deployment that predates the key keeps behaving exactly as it
does today.
nullrather than0for unlimited: zero would otherwise read as "no sessionsallowed", which is a plausible way for someone to try to remove a cap and lock
every user out. The schema refuses zero and any negative or fractional value, on
both the full config and a patch.
The server side of this is NIST 800-53 AC-10, concurrent session control. It is
also an operational concern wherever workstations are shared, since an unbounded
session count leaves sessions alive on machines a user has walked away from.
This publishes the key. Enforcing it is the consuming server's job.