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

VpcInstanceAuthenticator uses wrong version, no option to change it #230

Closed
smirnovigor opened this issue Jan 5, 2023 · 5 comments
Closed
Assignees

Comments

@smirnovigor
Copy link

Hi all, I'm using ibm-cloud-sdk-core (v4.0.2), when trying to authenticate with VpcInstanceAuthenticator, getting "Caught exception from VPC 'create_access_token' operation: The version value cannot be before 2022-03-01".

From debug I see that '2021-09-20' passed by default, I don't see any option to change it.

@padamstx padamstx self-assigned this Jan 5, 2023
@padamstx
Copy link
Member

padamstx commented Jan 5, 2023

Looking into this now...

@padamstx
Copy link
Member

padamstx commented Jan 5, 2023

@smirnovigor A fix is available in this PR (branch = fix-vpcauth). It might take us a day or so to get this tested in a real VPC environment, but if you'd like to try out the fix by using the "fix-vpcauth" branch feel free to do that.
Here is a link to the npm docs on how to define a dependency on a specific branch:
https://docs.npmjs.com/cli/v8/configuring-npm/package-json#git-urls-as-dependencies

@smirnovigor
Copy link
Author

Thank you, it works fine, waiting for release

@padamstx
Copy link
Member

padamstx commented Jan 9, 2023

Thanks for giving that a try. We'll get this fix delivered soon.

@padamstx
Copy link
Member

padamstx commented Jan 9, 2023

The fix has been delivered in version 4.0.3 of the node core.

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

No branches or pull requests

2 participants