We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This feature is implemented in jwt-encoder-cli. Would be nice to have as part of the jwt-cli.
jwt-cli
The text was updated successfully, but these errors were encountered:
troyharvey#2 implementation
892277c
btw we can now do things like:
npx alexanderankin/jwt-cli#encoding encode --header.alg RS256 --verbose
and it will produce:
$ npx alexanderankin/jwt-cli#encoding encode --header.alg RS256 --verbose --body.sub john --body.scopes "openid read.profile" { "message": "printing generated key because verbose mode is selected", "secret": "-----BEGIN RSA PRIVATE KEY-----\nMIICXAIBAAKBgQCwR7pyMatqVRu7gwydBTMv5sh2YEuXt3szd2/kLv0DpHBm1gH6\niH1Fajzm6pkM7JEy1DXTJLGw81X4xjYPtGs4qqBModr+7qGNtLaz4O8lk+k/N9T8\nUd7JoA5Whkzn7qa+iyCa8TJgN0XKG9PLiSHa1moV042b5v7gtDhsoxKkEQIDAQAB\nAoGAHyJcDMU3CE3F2yV3OdhsRP6W00mIsGAos1tZ+MxPxa/qZk9QBCbNMVBlN0ei\nBoVV08tlQkiN1bn0qj6f18A+23VDSgO4FwZNMQnqAsj7R3TqzosmmGGPa9mIpIl4\nZTkpv+bbKKJ+T8aU2jL+42SVsnB/Rdq4Xa7dBYZUI5nFY/0CQQDXZrTf5OZ6RwhI\nrdfFbyW0iooEqKejx2bQpQeS5p2BIdzXwCL/seQthWfRiVs+RZPGGunGztjd6IzI\n00PFMQk3AkEA0YFmPQQUMw9+eZz1m6oZkVYuxqTPd9f38ZIXA+wUvQdpnbkq3+Xz\nHcwh+nhMyOaxqVzav8vpjr6ay6pMO7NA9wJAQhKgMvmc9S8qzFh/EnHop/vDIHC3\nk5aL5D5rF1WkRMMlYgzu724a5xe/49d1ZKGlFaSVx0UV4uP9o3Cini9PewJAGsAa\n/c93hM2FqKGR+r5NZXFLp7GDjBnXXtD4f1e1ji1UHv91qgECeduGuySBKWXLaYSh\nqbuvprpPqZGlCjppIQJBAMa3FEwG8HDFRcDQj11GZddkXX8LUx9Byk6Y+A5kEkOp\nkOUNQ1f5tafq19RWidQp2kzhr1C7rrFm/AHv8uT3T2M=\n-----END RSA PRIVATE KEY-----\n", "generatedPublicKey": "-----BEGIN RSA PUBLIC KEY-----\nMIGJAoGBALBHunIxq2pVG7uDDJ0FMy/myHZgS5e3ezN3b+Qu/QOkcGbWAfqIfUVq\nPObqmQzskTLUNdMksbDzVfjGNg+0aziqoEyh2v7uoY20trPg7yWT6T831PxR3smg\nDlaGTOfupr6LIJrxMmA3Rcob08uJIdrWahXTjZvm/uC0OGyjEqQRAgMBAAE=\n-----END RSA PUBLIC KEY-----\n" } eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJqb2huIiwic2NvcGVzIjoib3BlbmlkIHJlYWQucHJvZmlsZSIsImlhdCI6MTcwMDk2NDM0NX0.nlj-dNuLp9uIsP2qMkUnXliO9fht5rvyBG_50lVjdbFL7RkvX2tuCQP4a_kvJDCLbcdmnruOOPWtrNv2sANCrQt9AUR5YMfuRs-zWXfsiUhO7QT8u0hX0J_ly2VnmdyHMPiLUhKZwbcONaCZVL-dMMXrX-gZFFWg2X1v82Kg9oo
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
This feature is implemented in jwt-encoder-cli. Would be nice to have as part of the
jwt-cli
.The text was updated successfully, but these errors were encountered: