I don't know if I'm missing something, but I've carefully followed Hubspot's API documentation and have successfully integrated my codebase with a "Test Hub", using cURL and PHP, but I cannot figure out how to now point this to the live hub? Where do I get the Client ID and Client Secret from my live Hubspot account? Or at least connect my live site to the app I have created?
Ok so apparently you have to have a matching developer account email address as the one that is in the Hubspot account. That is, if you are a developer, you have to also have an account inside of the Hubspot instance you are connecting to.
Thanks BAD UI and documentation.
Related
First we took the SAML code sample references from https://github.com/onelogin/php-saml and set up the integration with our project.
Before going to company SSO, we created trial account with a third party service provider one login, to test our code for Single sign on is proper.
On local this worked perfectly. We deployed same on GCP with changed references and test failed.
Next we went with our company SSO on GCP with certificates and necessary changes. It failed in similar manner as as not authenticated
When the site is accessed redirection to company sso OK
Successful Authentication at company SSO and redirection back to Application OK
Validating the response from company SSO in the application NO
On using SAML Tracer it was clear that the authentication at the company SSO side was proper, only that our code wasn’t able to receive it properly.
Since on local things are working as intended we doubt with respect to GAE/PHP we may be missing something as the application cannot verify the object returned from SSO, may be losing cache/session.
we are using Google app engine standard with our application being PHP 7.4
I keep getting 401 in spite of using the test keys from the playground app, can someone help on how to resolve this, code works fine on a dev server, as soon as code moved to qa server i created a new QuickBooks account and a new app and now i keep getting a 401
Just moving code from one server to another is a guaranteed way to break anything OAuth related.
You would need to at least:
Move the code
Change the OAuth URLs in Intuit's control panel to point to the new server
Change the OAuth URLs in your code
Clear any stored OAuth access tokens from your database (if you moved the data in the database to the new server as well)
Reconnect to QuickBooks, via the [Connect to QuickBooks] button
Additional notes:
Why are you using test keys from Intuit's playground app? Create your own app, and use your own keys.
If you created a new app, you'll also need to swap our your OAuth consumer key, OAuth consumer secret, and App token in your code.
Be aware that if your app is in DEVELOPMENT mode, then you can only connect to DEVELOPMENT QuickBooks accounts. If you created a LIVE QuickBooks account, you can only connect to it with PRODUCTION/LIVE app credentials (e.g. you need to PUBLISH your app).
Since you didn't post:
Your code
Screenshots of the credentials from Intuit's control panel (assuming they are dev/sandbox and thus safe to post)
Any of the HTTP requests/responses you're sending/receiving
We won't be able to really help you much further.
I try to make a validation of purchases on the server, but it can't to make a request to Google Play Android Developer API. After a request it shows this one:
Error calling GET https://www.googleapis.com/androidpublisher/v1.1/applications/my.app.id/inapp/my_in_app_purchase/purchases/purchase_token: (403) Forbidden
If I make a validation of this purchase by the test form in Developers Console, everything is OK and Google API would send a response.
Requests to other API (for example Books API) works fine.
To work with API I use Google APIs Client Library for PHP. Authorization goes by Service Account. In Developers Console access to Google Play Android Developer API is on.
Ok I found the solution!
You must to connect your API with your app. You must go to your Google Play publish page (https://play.google.com/apps/publish) and invite a user with the service account email in Settings->User account & rights->Invite new user and give it the privileges of "View financial reports".
Thanks works for me, good luck!
I am trying to implement Push Notification using GCM,
Besically i am trying to send Notification to the GCM using my PHP server which will deliver it to my android application.
I have used code at androidhive!
The device is getting registered successfully but i am not receiving any notification at my device nor anything is visible at Google console.
I am not receiving any response from the link used https://android.googleapis.com/gcm/send or https://android.googleapis.com
Is there anything wrong in this approach?
Can anyone suggest me any authentic source for this?
Realizing that some people are facing issues implementing GCM. I have decided to post solution.
The example on AndroidHive is working perfectly. Its just the matter of correct configuration.
Replace project ID in Android app. (You can get project ID from you google's console link i.e google.com/apis/console/#project:xxxxxxxxxxxx:access)
Replace Server API Key on PHP Server(config.php)
Key for server apps (with IP locking).
You can get your IP from WhatIsMyIP.
Key for browser apps (with referers) will not work.
I need to implement push/C2DM notifications on my website, I installed the Android 3.0 platform sdk, simulator, and I installed the application from an .apk file.
Now, I'm using a ZF powered sites and I want to test my notification, is it possible through the simulator?
I didn't write the actual Android Application, and I'm not able to do anything on it, but what should I know to use it with PHP?
Thank you
You cannot push C2DM messages to third-party applications - not without their active participation. Google's technical implementation explicitly forbids that.
An app specifies a Google account it wishes to receive notifications from; in order to send notifications, you need to log on with a Google account. For everything to work, the account has to be the same. So unless you know what account does the app wants messages from, and you know the password to that account, no C2DM for you.