Skip to content
New issue

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

js: IAM support phase I (apikey) #147

Closed
srl295 opened this issue Mar 19, 2019 · 1 comment · Fixed by #151
Closed

js: IAM support phase I (apikey) #147

srl295 opened this issue Mar 19, 2019 · 1 comment · Fixed by #151
Assignees

Comments

@srl295
Copy link
Contributor

srl295 commented Mar 19, 2019

Tracking: IBM-Cloud/gp-common#24

This version will only use the gp specific API-KEY auth header, and not do any token management.
A future issue will handle token management and disable API-KEY.

@srl295 srl295 self-assigned this Mar 19, 2019
@srl295 srl295 changed the title IAM support js: IAM support Mar 19, 2019
@srl295
Copy link
Contributor Author

srl295 commented Apr 15, 2019

As a workaround, you can go into the GP dashboard (or using the rest API) and create an API user, and that will give you credentials you can use with the JS client.

srl295 added a commit that referenced this issue Apr 16, 2019
@srl295 srl295 changed the title js: IAM support js: IAM support phase I (apikey) Apr 17, 2019
srl295 added a commit that referenced this issue Apr 17, 2019
- iam_endpoint and apikey required
- new CLI options and variables
- test updates
- docs

Fixes: #147
srl295 added a commit that referenced this issue Apr 17, 2019
- iam_endpoint and apikey required
- new CLI options and variables
- test updates
- docs

Fixes: #147
srl295 added a commit that referenced this issue Apr 17, 2019
* iam: Phase I: use API-KEY for interim iam support

- iam_endpoint and apikey required
- new CLI options and variables
- test updates
- docs

Fixes: #147
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant