I'm having some trouble with the GCP console, hopefully someone can point me in the right direction.
A couple of days ago I generated some API Keys and was able to restrict their validity scope by target API. The form looked like this, and I was able to restrict keys to apply on my GAE private APIs only:
whereas today the righthand side tab has disappeared on me and I can only apply "Application restrictions" (IP range, referrer, etc..) and I can see merely the following menu.
I was and still am the owner of the project, and I'm not aware of any change in roles/project config/etc.. (although I can't 100% rule them out)
There is next to zero documentation about the mysterious "API restrictions" tab. Hope someone can help.
Many thanks in advance
F
This feature has been removed temporarly because was causing issues with the Google Maps API.
API already created making use of these restriction will not work and the workaround is to remove them and recreate them with no restriction.
https://issuetracker.google.com/issues/69715011
Please star the bug to add your vote and subscribe to notifications from Google. Hopefully they will fix the issue soon.
Related
I've enabled a G Suite Marketplace SDK but initially I set the Visibility to "My Domain" so I could test in isolation on my domain. Now I want to set it to Public but that setting is disabled.
Warning: Once you select and save a visibility setting, you cannot change it later. (https://developers.google.com/gsuite/marketplace/sdk)
However I can't even disable/delete that API configuration and recreate it, so I can set it to public.
Is there any way to change this GSuite Marketplace API configuration to Public? (without having to tear down the entire Google Project and all it's API configurations and start over... seems there should be a better way)
Thanks
Try to access your Developer Dashboard and click the edit part of your item. You can check there if you can set the visibility option of your item.
I think once you change it, it will undergo a manual review and you need to wait some time to be approve.
I contacted Google support and confirmed that the only way to resolve this is to create an entirely new app and choose Public the first time you save it. I hope that helps.
I'm using DotNetKit 1.2.6.5 and SagePayIntegration.Validation() is rejecting a customer email that uses the new .online domain (eg: foo#bar.online) with
CustomerEMail is invalid.
Is this fixed in 1.2.6.7 or is the source code for SagePay.IntegrationKit.DotNet.dll available somewhere so I can fix it?
Despite access to the source code (many thanks to #DavidG) SagePay Support have confirmed that the actual Gateway does not support all these new domains - so even if I modified the DotNetKit it would still be rejected by the Gateway.
SagePay support were very helpful but ultimately the
"... email domain foo#bar.online is not yet supported on our gateway.
We run development sprints continuously and although there are some
domains we may not yet support, we look to in future, dependent on
impact and demand..."
The SagePay Integration Kit uses this regex to validate email addresses:
[a-zA-Z0-9!#$%&'*+/=?^_`{|}~-]+(?:\.[a-zA-Z0-9!#$%&'*+/=?^_`{|}~-]+)*#(?:[a-zA-Z0-9](?:[a-zA-Z0-9-]*[a-zA-Z0-9])?\.)+(?:[a-zA-Z]{2,4})\b
Which does unfortunately not allow extra long TLDs. Fortunately I have the source code for the kit and I've added it to my GitHub account (along with a bug fix which is why I had to get it in the first place as SagePay are not updating it). You can find it here:
https://github.com/WiredUK/SagePay.IntegrationKit
And the Regex you need to edit is this file:
https://github.com/WiredUK/SagePay.IntegrationKit/blob/801f61cf965c391a98a025aa632949719084cef0/ApiRegex.cs
For info, you need to edit the very last part of the expression from 2,4 (which matches 2 to 4 characters in the TLD) to allow more, for example 2,30.
Edit: And just because I can, I opened an issue and fixed it.
I am trying to add applications into Brooklyn catalog. can anyone explain steps to add a new application to catalog.xml?
I did try the sample catalog provided at https://brooklyn.incubator.apache.org/v/0.7.0-M1/use/guide/quickstart/policies-and-catalogs.html . The application gets listed in catalog tab but when I try to launch it, it gets stuck at 'configuring'. Is there something else that needs to be done ?
I tried adding existing application to catalog ( https://brooklyn.incubator.apache.org/v/latest/ops/catalog/index.html ) but it failed. Can anyone help me with this ?
I'd strongly recommend upgrading to 0.7.0-M2-incubating, as the catalog has significantly improved since 0.7.0-M1. The documentation at https://brooklyn.incubator.apache.org/v/latest/ops/catalog/index.html describes the steps for 0.7.0-M2-incubating; they will not work for 0.7.0-M1.
The link to an explicit version of the docs (rather than latest) is https://brooklyn.incubator.apache.org/v/0.7.0-M2-incubating/ops/catalog/index.html
There are also more improvements in snapshot (and in existing pull requests), if you fancy trying the bleeding edge!
For the 0.7.0-M1 error "gets stuck at configuring", we'd need more info (e.g. logs, etc). Suggest you e-mail the mailing list or jump on IRC if it's still a problem (https://brooklyn.incubator.apache.org/community/mailing-lists.html).
I am curious if there's still possibility to create global keys for reCaptcha.
Documentation points it is possible, but I can find no way - no such option is there whenever I add a site.
Google made reCaptcha Global URL possible again in 2016 for the I'm not a Robot checkbox:
https://developers.google.com/recaptcha/docs/domain_validation
Now to get the keys to work on every URL you have to go to: "Advanced Settings" for your key, and untick the "Domain Name Validation" box:
https://www.google.com/recaptcha/admin
This is a security hole, so you are required to check the hostname field in your JSON response and reject any solutions that are coming from unexpected sources:
https://developers.google.com/recaptcha/docs/verify#api-response
This option has dissapeared. In fact, google is deleting that info from documentation step by step. There is an issue
Maybe we can ask to reopen that option, or at least, to obtain some info why this option its gone
Well the Secure Token would be the way to do this:
"A reCAPTCHA key is normally tied to a set of individual domains. However, you might have a large number of hosted domains and would like to have one key working on all of them - the solution is the secure token."
https://developers.google.com/recaptcha/docs/secure_token
A similar question (How can I use reCAPTCHA v2 on a large number of domains?) has a PHP sample and a Java sample is in GitHub https://github.com/google/recaptcha-java/tree/master/appengine
I don't see any updates to the github for 8 months: https://android.googlesource.com/platform/frameworks/uiautomator/
There are uiautomator defects filed in https://code.google.com/p/android/issues/list?can=2&q=uiautomator
Is it safe to say that Google has dropped support for this tool?
PS: Is there an email address or contact # that I could get this information from a Google representative?
A quick check shows that the members are still assigning the bugs and enhancements. Check this one for example:
https://code.google.com/p/android/issues/detail?id=82292&q=uiautomator&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
I don't think it is being dropped.