adobe / aio-cli-plugin-jwt-auth Goto Github PK

View Code? Open in Web Editor NEW

4.0 25.0 8.0 107 KB

JWT Auth Plugin for the Adobe I/O CLI

License: Apache License 2.0

JavaScript 97.62% Batchfile 2.38%

adobe-io cli adobe adobe-io-cli adobe-io-cli-plugin

aio-cli-plugin-jwt-auth's Introduction

aio-cli-plugin-jwt-auth

JWT Auth Plugin for the Adobe I/O CLI

Usage
Commands

Usage

$ npm install -g @adobe/aio-cli-plugin-jwt-auth
$ ./bin/run COMMAND
running command...
$ ./bin/run (-v|--version|version)
@adobe/aio-cli-plugin-jwt-auth/2.0.4 darwin-x64 node-v10.18.1
$ ./bin/run --help [COMMAND]
USAGE
  $ ./bin/run COMMAND
...

Commands

./bin/run jwt-auth:access-token

`./bin/run jwt-auth:access-token`

get the access token for the Adobe I/O Console

USAGE
  $ ./bin/run jwt-auth:access-token

OPTIONS
  -b, --bare                   print access token only
  -f, --force                  get a new access token
  -p, --passphrase=passphrase  the passphrase for the private-key
  --no-prompt                  do not prompt for passphrase

DESCRIPTION
  You must have a 'jwt-auth' key in your config, that has all your config data in .json format:
       aio config set jwt-auth --json --file path/to/your/config.json

EXAMPLE

  jwt_auth:
  {
     "client_id": "...",
     "client_secret": "..."
     "jwt_payload": {
       "iss": "...",
       "sub": "...",
       "...": true,
       "aud": "..."
     },
     "jwt_private_key": "/path/to/cert"
  }

See code: src/commands/jwt-auth/access-token.js

aio-cli-plugin-jwt-auth's People

Contributors

Stargazers

Watchers

Forkers

dalavancloud fmeschbe purplecabbage yu1986 isabella232 sandeep-paliwal shazron ghas-results

aio-cli-plugin-jwt-auth's Issues

An in-range update of @adobe/aio-lib-core-config is breaking the build 🚨

The dependency @adobe/aio-lib-core-config was updated from `1.2.0` to `1.2.1`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@adobe/aio-lib-core-config is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build errored.

Release Notes for path files were not included in package.json

fix: patch files were not included ba0cc71

1.2.0...1.2.1

Commits

The new version differs by 2 commits.

30404bb 1.2.1
ba0cc71 fix: patch files were not included

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @oclif/test is breaking the build 🚨

The devDependency @oclif/test was updated from `1.2.2` to `1.2.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@oclif/test is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Use aio-cna-core-config module (replace aio-cli-config)

https://github.com/adobe/aio-cna-core-config

resolve depcheck warnings

Unused dependencies
* @oclif/config
* @oclif/errors
Missing dependencies
* execa: ./e2e/e2e.js
* cli-ux: ./src/commands/jwt-auth/access-token.js
* node-fetch: ./test/commands/jwt-auth/access-token.test.js

ACNA-270 - access-token doesnt get a new token if one exists, even if the private key has changed

Expected Behaviour

if the private key has changed then the access token should be regenerated

Actual Behaviour

private key is not regenerated if it already exists

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Publish v2.0.1

blocked by adobe/aio-lib-core-config#6
update aio-cna-core-config dep to ^1.0.14

README links to command source code result in 404

Describe the bug
oclif/dev-cli has a bug where it assumes a version tag is prefixed by v when it should respect the setting in .npmrc. See oclif/dev-cli#123

Workaround is setting this key in the plugin's package.json:

"oclif": {
    "repositoryPrefix": "<%- repo %>/blob/<%- version %>/<%- commandPath %>"
  }

To Reproduce
See the section for a command in README.md, the link to the source goes to 404.

Expected behavior
The link works.

Actual behavior
The link does not work.

An in-range update of codecov is breaking the build 🚨

The devDependency codecov was updated from `3.6.4` to `3.6.5`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

codecov is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

✅ codecov/patch: Coverage not affected when comparing 44375df...e3a7142 (Details).
✅ codecov/project: 100% remains the same compared to 44375df (Details).
❌ Travis CI - Branch: The build errored.

Commits

The new version differs by 2 commits.

ebe132e 3.6.5
02cf13d [CE-1330] Escaping args (#167)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Add AppVeyor integration

Hook up AppVeyor to run the unit tests on Windows.

Support --passphrase flag

See: adobe/aio-cli#1

Convert to use jsonwebtoken
Support passphrase flag in the command, pass to the accessToken function
Add function parameter passphrase to accessToken function, pass to the jwt encode function
Update the docs (this is in code, will be published to README when npm published)

An in-range update of eslint-plugin-jest is breaking the build 🚨

The devDependency eslint-plugin-jest was updated from `22.5.1` to `22.6.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ Travis CI - Branch: The build errored.

Release Notes for v22.6.0

22.6.0 (2019-05-22)

Features

rules: add no-commented-out rule (#262) (14d83ef)

Commits

The new version differs by 9 commits.

14d83ef feat(rules): add no-commented-out rule (#262)
83ff198 chore: migrate no-jest-import to typescript (#259)
718c08c chore: upgrade @typescript-eslint
ca2aa27 chore: port lowercase-name to TypeScript (#258)
3df0058 chore(ci): run danger with lts version of node
48e3a59 chore: precompile with babel (#257)
8670804 chore: bump deps
05eb11a chore: fix lint error
dff6446 docs: link to eslint-plugin-jest-formatting

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Remove aio-cli-plugin-jwt-auth from CLI Core plugins and deprecate

We recently enhanced the CLI and SDK with OAuth2 and JWT support through:

Library based IMS integration: https://github.com/adobe/aio-lib-ims
Authentication plugin: https://github.com/adobe/aio-cli-plugin-auth

This plugin is then obsolete. Could we

Remove it from CLI Core
Deprecate it?

Add Travis CI integration

Hook up Travis CI to run the unit tests.

ACNA-254 - [tests] mock out the config file, remove the jest global setup/teardown

Mock using a fake filesystem.

An in-range update of eslint-plugin-jest is breaking the build 🚨

The devDependency eslint-plugin-jest was updated from `22.9.0` to `22.10.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ Travis CI - Branch: The build errored.

Release Notes for v22.10.0

22.10.0 (2019-07-17)

Features

rules: adds no-if rule (#293) (28bd1dc)

Commits

The new version differs by 7 commits.

28bd1dc feat(rules): adds no-if rule (#293)
7ebdc0e chore: enforce import destructure order
31c7cef chore: convert to import/export (#302)
9f858cb chore: delete tests instead of ignoring them with babel
c595ba0 chore: do not include tests in published tarball
4b4eb78 chore: fix lint error in md file
d3ea720 chore(docs): fix typo (#304)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

ACNA-253 - Add `codecov/patch` as a Required check for PRs

Settings ->Branches -> Edit (master) -> Require status checks to pass before merging
This will only show up if you have a new PR, since it was recently activated

`jwt-auth:access-token` config error should not show stack trace

Error: missing config data: jwt-auth
    at getAccessToken (~/git/adobe/aio-cli-plugin-jwt-auth/src/commands/jwt-auth/access-token.js:42:27)
    at AccessTokenCommand.run (~/git/adobe/aio-cli-plugin-jwt-auth/src/commands/jwt-auth/access-token.js:105:20)
    at AccessTokenCommand._run (~/git/adobe/aio-cli-plugin-jwt-auth/node_modules/@oclif/command/lib/command.js:44:31)
    at <anonymous>

ACNA-239 - Remove usage of Travis-CI.org Github Service Integration

This repo has been migrated to Travis-CI.com, and the Github App has been activated

Publish 1.0.7

Issues covered:
https://github.com/adobe/aio-cli-plugin-jwt-auth/milestone/1

An in-range update of @oclif/test is breaking the build 🚨

The devDependency @oclif/test was updated from `1.2.4` to `1.2.5`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

✅ codecov/project: 100% remains the same compared to be6d9c2 (Details).
✅ codecov/patch: Coverage not affected when comparing be6d9c2...246249a (Details).
❌ Travis CI - Branch: The build failed.

Release Notes for v1.2.5

chore(deps): bump lodash from 4.17.11 to 4.17.15 (#45) abccac6
chore(deps): bump js-yaml from 3.12.0 to 3.13.1 (#44) 0b80890

v1.2.4...v1.2.5

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

ACNA-255 - Use adobe/jwt-auth module for jwt actions

However, we need to send a PR to adobe/jwt-auth to support passphrases in private keys. This should be easy since both use the 'jsonwebtoken' npm module.

Use @adobe/jwt-auth 0.2.0 when is released

It will have this feature that unifies all the errors returned: adobe/jwt-auth#11 and will allow us to clean up the code a bit.

adobe / aio-cli-plugin-jwt-auth Goto Github PK

aio-cli-plugin-jwt-auth's Introduction

aio-cli-plugin-jwt-auth

Usage

Commands

./bin/run jwt-auth:access-token

aio-cli-plugin-jwt-auth's People

Contributors

Stargazers

Watchers

Forkers

aio-cli-plugin-jwt-auth's Issues

The dependency @adobe/aio-lib-core-config was updated from 1.2.0 to 1.2.1.

The devDependency @oclif/test was updated from 1.2.2 to 1.2.4.

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

The devDependency codecov was updated from 3.6.4 to 3.6.5.

The devDependency eslint-plugin-jest was updated from 22.5.1 to 22.6.0.

22.6.0 (2019-05-22)

Features

The devDependency eslint-plugin-jest was updated from 22.9.0 to 22.10.0.

22.10.0 (2019-07-17)

Features

The devDependency @oclif/test was updated from 1.2.4 to 1.2.5.

Recommend Projects

Recommend Topics

Recommend Org

`./bin/run jwt-auth:access-token`

The dependency @adobe/aio-lib-core-config was updated from `1.2.0` to `1.2.1`.

The devDependency @oclif/test was updated from `1.2.2` to `1.2.4`.

The devDependency codecov was updated from `3.6.4` to `3.6.5`.

The devDependency eslint-plugin-jest was updated from `22.5.1` to `22.6.0`.

The devDependency eslint-plugin-jest was updated from `22.9.0` to `22.10.0`.

The devDependency @oclif/test was updated from `1.2.4` to `1.2.5`.