We currently have a Server intergration with the sagepay API, when the time comes for the card details to be entered the user is redirected to the sage pay website which displays all the information in english. Does anyone know if its possible to specify which language sage pay uses to display information on its site ?
This will be available when the next protocol version is available as far as I know.
Regards.
Related
I am currently testing to implement account linking by voice.
This system works perfectly but I would like to leave the option to the user to give him the possibility to connect via a classic oauth web page. Is this possible? If yes, how to do it ?
I would really appreciate a link or a helper because I can't find anything :(
Thanks to you the community :)
I am trying to develop a contextual gadget, but not getting any documentation for it. Google provides a document which is very old and not updated from long time. Process explained in that documentation to develop a gadget is deprecated.
Please if anyone have solution, help me.
You may want to check full documentation in Gmail Contextual Gadgets which was last updated June 29, 2016.
To develop a Gmail Contextual Gadgets, you may want to first check the given implementation parts also discussed in the documentation. Then, you may go through these summary of steps:
Use JQuery, or write JavaScript that conforms to ECMAScript 5 Strict Mode.
Note: You need to be using the correct development frameworks to provide an extra layer of protection between your gadget's potential vulnerabilities and your end users. To find out why, see Using the right frameworks for security.
Choose one or more pre-canned extractors. This determines which type of content will trigger your gadget.
Write a manifest for the gadget.
Write the gadget spec. This determines what the gadget will do when it is triggered.
Publish the gadget spec to a location which is accessible on the public Internet. An intranet will not work. Your hard drive will not work. (Why? Google's servers need to download the gadget. If they can't reach it, then Gmail can't display it.)
Install the gadget.
Test the gadget by sending yourself some email. The gadget should appear in Gmail whenever you read an email that contains the right sort of content. For more tips on testing gadgets, see Publishing Your Gadget in the gadgets API site.
It will really help if you go through the documentation as there are best practices, limitations and important details that you should note.
This related SO post might also help.
I am developing a product which analyze Gmail account data and for that I need to allow user to log in to their Gmail account from my product. Now everything is going perfect no problem is there in execution. But when a new user come each time he/ she has to resolve Google Captch page (https://accounts.google.com/DisplayUnlockCaptcha). Now this is being hesitation to users and I want to skip this step. So is there any way through which I can eliminate this step?
Please help, thanks in advance.
Thanks,
Anvesh
After a long research I came to know that I can my domain to Google account which will allow me to register my web application. Anyone can register through this link https://accounts.google.com/ManageDomains
It's just simple many documents available for guidance.
Thanks,
Anvesh
I'm making an app and I plan to have some cloud happening with it, but I do not want to create a user data base and have the users need to remember their username and password.
Since it will be distributed through the chrome app store it's basically guaranteed that the user will have a google account. All I want to do is:
Get the user's email through the google account stuff. If I get it through there, well then their email is all the authentication I need to get that user's data.
If I end up putting the application on something other than chrome browser, I'll just have the user use their email to request a validation link, and then I'll send them a validation code for that account, they put the validation code into the application, it takes that as a verified user, so that's secure and easy as well.
EDIT: I'm looking into this. So far I have:
OAuth 2
Google API
But I have a problem that I don't know what to set as my javascript origins in the Google API and there isn't too much info on this abroad. If anyone can tell me what javascript origins I need to set for a chrome extension to access google api it would be a great help.
PS: Thanks for down vote, this is why I love resorting to stack exchange.
Hmmm, I think the only reason this was voted down is the fact that this question may be been asked somewhere on the site already (but I'll help you and give give a 1up).
So what you are wanting to use the Google OpenID. You will have to register your application with Google so they can provide OAuth2 tokens for you application. I have not done this with Google but with other services and it is pretty easy, just search around.
In terms of obtaining OAuth2 for your application in the chrome extension - this can be a pain since the extension is sandboxed and Google's example uses OAuth not OAuth2.
Here is solution I host on GitHub for this - I also use this in my extension GitHub Repositories:
https://github.com/jjNford/oauth2-chrome-extension
Hope this helps in some way. Don't get discourages with StackOverflow, it is a great resource with many great contributors.
Good luck!
I had to up vote you too as I'm tracking down a related issue so here is what I've found that may help.
According to these directions - http://code.google.com/p/google-api-javascript-client/wiki/Authentication - "In the "Authorized JavaScript Origins" box, enter the protocol and domain for your site." This should be the protocol (http:// or https://) followed by any optional subdomain followed by your domain name and no trailing slash. Nothing after the domain name.
This prevents certain kind of security attacks, see: http://en.wikipedia.org/wiki/Same_origin_policy.
There are some related questions here that I found that may help:
Problems with Google Picker API and selecting Google Drive items and google apis console 'Javascript origins'.
Now with all of that said, I am still trying to track down what values to put in there for one of my sites hosted as a Google Site, as none of the obvious values are working for me. So there may be some subtlety there that I have missed in this explanation.
How can I sniff out desktop users and send them to regular (non-mobile) site when they find the mobile site listed in google?
Thank you for any insight!
You can check the HTTP-headers for the type of browser the user is using and redirect to the correct site. There is also a nifty framework for it; http://detectmobilebrowsers.mobi/
Dave,
There's a really interesting article about it on Google Central. You should check it out.
While I'm aware that it doesn't answer your question, it's totally worth reading. As I'm on this very same quest, I'd appreciate if you could share with us whatever way out of this predicament you get to find.
By the way, can you post your website URL here for the rest of us to see? :-)
You could use www.handsetdetection.com in reverse to redirect people from your mobile site back to your standard site.