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.

Sign up for GitHub

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

Jump to bottom

/verifyApiKey returning 500 causing proxy verification failure #139

Closed
rockspore opened this issue Dec 23, 2020 · 1 comment · Fixed by #140
Closed

/verifyApiKey returning 500 causing proxy verification failure #139

rockspore opened this issue Dec 23, 2020 · 1 comment · Fixed by #140
Assignees
@rockspore
Labels
bug Something isn't working

Comments

@rockspore
Copy link
Contributor

When the policy secret doesn't exist, /verifyApiKey returns 500. This is failing the proxy verification. We need to allow 500 status code. It will be a quick fix.
@rockspore rockspore added the bug Something isn't working label Dec 23, 2020
@rockspore rockspore self-assigned this Dec 23, 2020
@rockspore rockspore mentioned this issue Dec 23, 2020
Merged
@rockspore
Copy link
Contributor Author

This scenario is specific for a newly provisioned proxy on an Apigee Hybrid cluster where no existing secret is present.

The runtime seems to keep existing secrets (even if the k8s secrets are deleted) for quite some time so it may not be common to see this problem in a cluster that was provisioned before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rockspore rockspore

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

allowing 500 for /verifyApiKey apigee/apigee-remote-service-cli
1 participant
@rockspore