The repository master branch has been renamed to main. If you have a fork or a local copy of the repository, you would have to perform the following git operations:
git checkout master
git branch -m master main
git fetch origin
git remote set-head origin -a
Added
IssueUserJWT() takes an account scoped signing key, account id, and use public key (and optionally a user's name, an expiration duration and tags) and returns a valid signed JWT. See the following ADR for more information (#163)
JetStreamLimits.MaxBytesRequired: a boolean to indicate that max_bytes is required for all streams created under an account (#164)
AccountClaims.Limits.JetStreamTieredLimits: which is a map of JetStreamLimits where the key is the tier, for example "R1", "R3", etc.. (#169)
JetStreamLimits.MemoryMaxstreamBytes and JetStreamLimits.DiskMaxstreamBytes: to limit the maximum value for max bytes for memory and disk (#172)
JetStreamLimits.MaxAckPending: to limit the number of MaxAckPending on a consumer (#174)
AccountLimits.DisallowBearer: to reject connections from user JWTs that have the bearer token boolean set to true (#177)
Fixed
Activation's validation error text: was reporting invalid export type instead of invalid import type (#176)
Two new connection types, LEAFNODE_WS and MQTT_WS (not yet supported in the NATS Server, but will be in the near future). If the administrator wants to restrict a configured user to a leaf node connection (websocket or not) but not as a standard user (a client application), the previous existing connection types would not allow it. Having only LEAFNODE would not deny LeafNode connection over websocket, and adding WEBSOCKET would then allow client applications to connect to the client websocket port (#161)
Fixed
Decoding of signing keys would return a nil map instead of the actual signing keys (#160)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/dmwm/WMArchive/network/alerts).
Bumps github.com/nats-io/jwt from 1.2.2 to 2.4.0+incompatible.
Release notes
Sourced from github.com/nats-io/jwt's releases.
... (truncated)
Commits
11e1fdbBump version for imminent release: 2.4.07018e50Merge pull request #189 from nats-io/simplify-response7b33986added additional scrutiny to DidSign in the case of signing keys (#190)e3e39d6overhaul jwt v2 and v1 inter-tangling (#195)8d1c62fadded additional scrutiny to DidSign in the case of signing keys (#190)f135d4a[chore] migrate ci to gha (#191)bdf40faMerge pull request #186 from nats-io/auth-updates146945dAdded in a formal authorization response for propagating errors back to a NAT...ff7baa9Merge pull request #185 from nats-io/user-nkey1ddeceeForce authorization requests to have a public user nkey.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/dmwm/WMArchive/network/alerts).