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

Unable to create client: could not create oidc provider (sample config file for version 1.4) #187

Open
divyav opened this issue Jul 29, 2020 · 5 comments

Comments

@divyav
Copy link

divyav commented Jul 29, 2020

I am using version 1.4. I get the following error: Unable to create client: could not create oidc provider

Is there a different version of the config file required to run 1.x versions.

@divyav divyav changed the title Unable to create client: could not create oidc provider (sample config fil for version 1.4) Unable to create client: could not create oidc provider (sample config file for version 1.4) Jul 29, 2020
@edulop91
Copy link
Contributor

Hey @divyav , thanks for reachign out! We are in the process of open sourcing the Bless lambda replacement that relies on oauth/oidc for federated access (rather than AWS IAM keys). Until then, you should be able to use one of the 0.x releases. Let me know if those work.

@divyav
Copy link
Author

divyav commented Jul 29, 2020

Noted. Thanks! I will try the 0.x release.

@divyav
Copy link
Author

divyav commented Jul 29, 2020

I installed 0.6.1 version. I referred to the solution provided here to fix the KMSAuthError. However, now I get:

FATA[0000] 1 error occurred: * Error requesting kmsauth token: KMS encryption failed: UnrecognizedClientException: The security token included in the request is invalid

The ssh_exec_command I am using is: 'aws-vault exec divya --no-session -- blessclient run'

Is this the right way to use it?

@edulop91
Copy link
Contributor

Would you be able to double check if you can perform encryption (maybe by verifying the policy) with your kmsauth kms key?

@csanders-git
Copy link

Any update on this? Is the updated project now OSS?

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

3 participants