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

UnrecognizedClientException error when changing Access & secret key #234

Closed
iwysiu opened this issue Jul 26, 2023 · 0 comments · Fixed by #235
Closed

UnrecognizedClientException error when changing Access & secret key #234

iwysiu opened this issue Jul 26, 2023 · 0 comments · Fixed by #235
Assignees
Labels
datasource/Redshift effort/small up to 1 day good first issue Good for newcomers type/bug Something isn't working

Comments

@iwysiu
Copy link
Contributor

iwysiu commented Jul 26, 2023

This is the same issue as grafana/athena-datasource#246 , just in Redshift. Similarly, it can be reproduced by:
-create an IAM user with an access and secret key
-use those keys to create a Redshift datasource
-run an explore query with a schema selected
-create a new IAM user with the same permissions
-delete the old IAM user
-save the datasource with the keys from the new IAM user
-run an explore query with a schema selected (this should error)

It can be fixed the same way as grafana/athena-datasource#262 , by adding the updated time to the sqlds.Options passed to awsDS.GetDB, awsDS.GetAsyncDB, and awsDS.GetAPI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
datasource/Redshift effort/small up to 1 day good first issue Good for newcomers type/bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant