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

Need a server-side API to validate keys, especially the public one #163

Closed
davemerrill opened this issue Jun 7, 2017 · 3 comments
Closed

Comments

@davemerrill
Copy link

davemerrill commented Jun 7, 2017

Many applications prompt for reCAPTCHA keys, save them, and use them to generate the UI as needed. Ideally we'd be able to validate those keys before accepting them.

We can validate the private key by submitting an empty response to the verification API, and if 'invalid-input-secret' isn't in the 'error-codes' array in the result, the private key is valid. That's a bit indirect, but workable.

However, the verification API doesn't take the public key as a parameter, so it can't be validated that way. Best I've been able to figure out is to use the public key to show the reCAPTCHA UI on the client, and ask the user to confirm that it displayed correctly.

Some server-side way to test that the public key is valid for this domain would be vastly preferable. Ideally we could test both keys at once, without the fake verification step above.

@rowan-m
Copy link
Contributor

rowan-m commented Jul 29, 2018

Closing super old issues. Please re-raise if still relevant.

@rowan-m rowan-m closed this as completed Jul 29, 2018
@davemerrill
Copy link
Author

I'm not working on that project any more, but it still seems pretty relevant to me, for the reasons stated.

@davemerrill
Copy link
Author

This issue doesn't appear to be getting any traction. Could someone on the dev team please explain to me what existing techniques there are to procedurally validate the public and private keys before saving them in the above scenario, or why that's not necessary?

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