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

[Bug] Calls to Source Cooperative API call unimplemented route when empty AWS_ACCESS_KEY_ID is provided #5

Open
kbgg opened this issue Oct 26, 2024 · 0 comments
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed

Comments

@kbgg
Copy link
Contributor

kbgg commented Oct 26, 2024

Description of Bug:

Authentication calls to the Source Cooperative API call an unimplemented route when an empty AWS_ACCESS_KEY_ID is provided to the data proxy.

Steps to Reproduce:

  • Run data.source.coop locally
  • Set AWS_ACCESS_KEY_ID environment variable to empty value (i.e. export AWS_ACCESS_KEY_ID=)
  • Call any data proxy operation using the AWS CLI (i.e. aws ls s3://planet/rapidai4eo/ --endpoint-url=http://localhost:8080)

Expected Behavior:

Authentication method does not call the {$SOURCE_API_URL}/api/v1/api-keys/{API_KEY}/auth endpoint as we already know the user is making an unauthenticated request.

Actual Behavior:

Calls are made to the {$SOURCE_API_URL}/api/v1/api-keys/auth endpoint since the reqwest library transforms the request path from /api/v1/api-keys//auth to /api/v1/api-keys/auth. These requests cause a 501 - Not Implemented error on the Source Cooperative Frontend & API

Additional Context:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant