nats-io/nsc

Issues

• prune local

  #659 opened 4 months ago by tommyjcarpenter
  3

• enhance automation capabilities

  #660 opened 3 months ago by davidovich
  0

• [FEAT] specify subject mapping as single option flag like "bar:50" allowing multiple copies of the flag

  #522 opened 5 months ago by aricart
  0

• NSC does not allow multiple clusters with 100% weight subject mapping

  #657 opened 5 months ago by vinicius-seedcx
  1

• MQTT Option in JWT

  #647 opened 6 months ago by aricart
  0

• Bad diagnostic for adding user without using signing-key when operator is strict_signing_key_usage

  #628 opened 6 months ago by philpennock
  0

• Operator key is not needed to create user, but is needed to delete user

  #652 opened 6 months ago by mikehardenize
  1

• nsc install.py does not recognize CPU architecture ARMv7L debian buster on Raspberry Pi 3B+

  #648 opened 6 months ago by dixon1e
  0

• Option to add custom claims to the generated jwt

  #651 opened 6 months ago by Zetanova
  4

• “nsc generate config --nats-resolver” will output extra commas in resolver_preload

  #650 opened 6 months ago by sinbane
  10

• trying to push remove or push prune stack traces with no error message

  #639 opened 9 months ago by tommyjcarpenter
  32

• The only way to enable jetstream for an account is by setting one (or more) limit(s) of the jetstream settings for that account

  #631 opened 9 months ago by anthonyjacques20
  1

• add compatibility with tracing

  #636 opened 9 months ago by aricart
  0

• nsc version on brew tap nats-io/nats-tools is outdated

  #635 opened 10 months ago by jnehlmeier
  3

• Add an option to create a scoped signing-key in one command

  #633 opened 10 months ago by BZValoche
  0

• [Artificial Loss ]subject_mapping ?

  #632 opened a year ago by chenjpu
  0

• Not able to install nsc on windows machine

  #629 opened a year ago by WAG10
  2

• New nsc version inlcuding latest nkeys vuln patch

  #623 opened a year ago by rubur-webbeds
  2

• nsc creates 2 keys for the operator and the SYS accounts

  #612 opened a year ago by VirgileD
  1

• nsc pull shows incorrect message when a newer account is present locally

  #607 opened a year ago by RafalGoslawski
  0

• Wrong output in `nsc reissue operator`

  #609 opened a year ago by RafalGoslawski
  0

• [FEAT] provide global option to generate JSON responses for every command

  #589 opened 2 years ago by aricart
  1

• Describe account does not enforce/indicate account token position on exports

  #597 opened a year ago by brianmcgee
  1

• tests should not fail when: $TMPDIR is set

  #563 opened a year ago by philpennock
  0

• Generating of description for entities in combination of `json` and `write to file` is broken

  #594 opened a year ago by Drakorgaur
  0

• `nsc add export` changes account issuer

  #582 opened 2 years ago by kimjarvis
  2

• nsc edit is checking if JetStream is available

  #569 opened 2 years ago by sty-holdings
  4

• `nsc generate creds` produces invalid creds file.

  #584 opened 2 years ago by ebusto
  3

• `nsc pull` does not sign a self signed account

  #586 opened 2 years ago by kimjarvis
  1

• `nsc generate nkey` outputs good response to stderr rather than stdout

  #580 opened 2 years ago by kimjarvis
  4

• `nsc import keys` has an invalid example.

  #585 opened 2 years ago by ebusto
  0

• Unable to set `nsc` signing key permissions for reserved `$` subjects

  #588 opened 2 years ago by AshleySchaeffer
  6

• `nsc add user` should not attempt to validate the account signing keys in the local keystore,

  #577 opened 2 years ago by kimjarvis
  4

• When an additional signing key is added to the operator, users on accounts issued by it observe Authorization Violation

  #575 opened 2 years ago by kimjarvis
  4

• `nsc add export` should not attempt to validate the account signing keys in the local keystore

  #579 opened 2 years ago by kimjarvis
  1

• `nsc edit account` should not attempt to validate the operator signing keys in the local keystore

  #581 opened 2 years ago by kimjarvis
  2

• Segmentation violation from `nsc import account`

  #578 opened 2 years ago by kimjarvis
  0

• nsc import user does not expect a decorated jwt

  #571 opened 2 years ago by kimjarvis
  5

• Upgrade `nats-io/jwt` to fix false positive vulnerability

  #535 opened 2 years ago by rubur-webbeds
  3

• Imports with the same name seem to get confused

  #521 opened 2 years ago by dylanratcliffe
  3

• $NSC_CWD_ONLY prevents what it promises

  #513 opened 2 years ago by jjthiessen
  1

• Creds file has an extra blank line in the armor

  #529 opened 2 years ago by aricart
  1

• go install github.com/nats-io/nsc/v2@2.7.6 fails

  #548 opened 2 years ago by gedw99
  1

• when same signing key is used in two accounts, adding an user on the second account will result in an error

  #546 opened 2 years ago by aricart
  1

• Can't not disable wildcard-exports in nsc

  #536 opened 2 years ago by nhatmicls
  2

• nsc add user -i is failing on `valid until` step - disregard issue - local to my system

  #545 opened 2 years ago by sty-holdings
  1

• Bug: Broken account database when using nsc in parallel

  #538 opened 2 years ago by joda01
  8

• nsc push should support wss/ws

  #544 opened 2 years ago by wenerme
  0

• Plan to adopt Go module versioning

  #530 opened 2 years ago by wallyqs
  4

• Follow Go module version numbering standards

  #523 opened 2 years ago by qjcg
  2