-
Notifications
You must be signed in to change notification settings - Fork 439
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
Authentication: hashed_account_id is deprecated #7506
Comments
Hello @ntward! Thanks for the comment. Do you have a link to the specific docs you are referring to? As well as a code example to help you debug? It does seem like the field you're trying to use is in fact deprecated. The link you shared to Stack Overflow links to the proto file: It gives the recommendation to use |
Hello, thanks for taking the time to respond! I was just putting together a code example. In doing so, I discovered that the minimal example worked just fine in my script, but not in my PHP app. On further investigation I realised that this is because in my app the global error handler rethrows errors as exceptions. The suggestion to use Here's a minimal example (credentials and tokens omitted for obvious reasons):
|
I believe this is the same issue as we've documented in protocolbuffers/protobuf#13428 I will try to fix this shortly |
Thanks for the update @bshaffer ! |
This has been fixed in the |
Hello,
I am using the Google\Cloud\RecaptchaEnterprise php API. I have been diligently following the docs, but keep hitting the same roadblock - I am beginning to wonder if this is an issue with the API...
I am using application default credentials with a service account key as described in the docs. I keep receiving the following error:
hashed_account_id is deprecated
As far as I can tell, there is nothing I can do as a user to resolve this - it is something internal to the library?
I see that others on StackOverflow have had the same issue:
recaptcha error hashed_account_id is deprecated
Any advice? I'm completely stuck.
Many thanks
The text was updated successfully, but these errors were encountered: