Hello to all
I am new in Amazon Alexa, I have a work to Alexa Skill account linking using PHP with oauth 2.0.
I have successfully configured all and also get code for Auth Code Grant but when I run my code in Chrome Browser it is generating Account linking Failed issue but when I run same URL in Firefox it generates Amazon linking failed with ERROR=missing-state.
Please help me to resolve my issue, any help would be highly appreciated.
Implementing Account Linking is tricky at times. The thing is at some point what happens between Alexa and the OAuth2 server is transparent for the Skill (Lambda), for example the process of refreshing a token among others, that is why I suggest you take a look at the references cited below.
Also because of the error shown, it seems that the parameter code is missing in one of the URLs exchanged back and forth between either the Alexa web console or Alexa mobile app and the OAuth2 server. Please verify it is always the same and is always present in the URLs. Implementing a proxy for sure will help on debugging this issue.
I would suggest you take a look at these great sources:
Debugging Account Linking
Using API Gateway to Debug Account Linking issues
I hope this helps somehow.
Cheers
Related
I am trying to access the Google Analytics API for web applications using PHP, like described in this tutorial: https://developers.google.com/analytics/devguides/reporting/core/v4/quickstart/web-php
I have followed all the steps precisely, however was not been able to make it running. I have managed to debug so far that I found out about where the problem is.
When OAuth consent screen pops up and I click Allow, application does not get authorized. I just keep seeing the same popup. Also, if I check authorized apps in my google account, it is not listed there.
Another interesting fact is that Hello Analytics Reporting API V4 using JavaScript is working just fine.
https://developers.google.com/analytics/devguides/reporting/core/v4/quickstart/web-js
Does anybody have a clue about what could be wrong with my app authorization?
OK, now I have additionally discovered it has something to do with localhost. Once I have uploaded the same code to live server, it is working just fine. But I cannot get it working on locahost. Does anybody have an idea how to setup Credentials or whatever to make it working in development environment (localhost)?
Check your browser extensions (i.e. Disconnect) may be blocking the auth token.
I'm using saml php toolkit and aiming to make azure as idp for authentication.! can anybody here . can help me for the idp configuration to submit and receive reply.
You can get started from http://azure.microsoft.com/en-us/documentation/articles/active-directory-authentication-scenarios/. It shows us a lot of scenarios. Based on your description, you have not described your scenario's details, so it is a bit difficult for us to provide more information at this stage. However since you're using SAML, I’d like to suggest you to look at the first scenario in the document: Web Browser to Web Application. Detailed registration guideline can be found at https://msdn.microsoft.com/en-us/library/azure/dn132599.aspx. After Azure registration is complete, it’s needed to follow the steps in http://developers.onelogin.com/v1.0/page/saml-toolkit-for-php to register in OneLogin. Please use the URL like https://login.windows.net/[TenantDomainName]/FederationMetadata/2007-06/FederationMetadata.xml instead of OneLogin's own identity provider URL. More information can be found at https://msdn.microsoft.com/en-us/library/azure/dn195583.aspx. Please feel free to let us know if you need further assistance.
I am implemented In App Billing for android.I wanted to implement subscription validity checking through my backend server. As Google Play Documentation, for making call for Google Play API,need authentication using oauth 2.0.
I followed instructions for registering project and creating credentials. But from there I have no idea how to use those credentials, I tried authentication via CURL request, but it asking permission as shown in follwing image
This permissions works fine I can exchange code and get access token, but all this done by manually, how should I implement this on backend.
I even try to use google api php library provided by Google, but It adds confusion. Also they didn't provide any example, how to use library.
Can anybody elaborate how exactly use library or pure php?
Thanks in advance.
To perform LVL and/or IAB validation on a server, do not access Google servers directly from the server. Even if all information were available, you would face integrity problems, because your app and your server will see different information due to synchronization latencies.
Instead, use your app as a proxy and validate the Google Play information on your server as described here.
Until recently we have been using the old gapi php class to extract Google Analytics data from a variety of sites that we manage.
In a nutshell at night the sites download the Analytics data and stores it locally. Until recently it worked beautifully but all of a sudden we started receiving all sorts of weird errors like CaptchaRequired.
Anyway I've done some reading and got the impression that it was time we move to the new Google APIs platform and while I have tried to follow the HelloAnalyticsAPI tutorial we initially got a 403 error but now after leaving it for a while when I try and run the app I get redirected to Google to login.
I just don't seem to be able to get my head around it. We need to completely automate this process so redirecting to login on the Google site isn't going to cut it.
Can anyone help? Anyone seen these issues?
Use google api client for php, it's easy
http://code.google.com/p/google-api-php-client/
And dev guide for analytics (V3):
https://developers.google.com/analytics/devguides/config/mgmt/v3/
Google sends Captcha responses if they are unsure about the authenticity of the request. This can be caused by multiple requests from the same IP for various different accounts, use of the ClientLogin authentication mechanism, and even weak passwords on the account you are logging in to.
To prevent them, I would recommend using OAuth 2.0 for the authentication - there are other security benefits to using this too.
we have developed an application that use push notifications by following the very good guide created by David Mytton.
The push service worked great on the development profile. But now that it is finished we have changed to the customers distribution profile. The application is an in-house application using an Enterprise account.
We have changed the certificate on the server and we have changed to the production url as specified in the tutorial. We have also replaced the profile used when building the application and installed it to the tester iPhone. Everything seems to work on the server, and no error messages is returned but the push is never recieved on the iPhone. We are pretty clueless right now and don't know where to start debugging on this. We have checked that the tokenId is updated after replacing the profile.
Has anyone any experience in this and might know what's wrong or where to start debugging? Thanks!
I have no idea what was wrong here but i finally got it to work..
After hours of debugging without results i threw in the towel and created a new developer certificate, app id, push sertificate and distribution profile. I cleaned the project added the new profile and replaced all files on server.
And it worked! No problems at all... Sometimes i hate being an iPhone/Apple developer :\
A few things that you could try:
Make sure your phone is plugged in to a power source (sometimes not having this causes delayed notifications).
Use the following PHP library:
http://code.google.com/p/php-apns/
This allows you to debug the communication with the server and see where the error occurs. Specifically it allows you to debug if your token id is incorrect.
You could try using an incorrect token id on the server and see the behavior. Compare this with using the correct token id.
Any in-house distribution profile gives out a same tokenID, how ever
this tokenID varies across different devices.
Other only issue could be only with the ProductionURL.
I have also notices that the push notification reception is delayed sometimes, mostly when used with production URL.
Hope this helps.