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
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 :)
Tried to search for my favorite character when I was just shocked with the change.
Can someone provide more details?
Personal is a new option of Google Search that is not integrated
directly in the algorithm that determines which search results are
returned to users when they run searches on Google.
It is a new option under the more link instead which you can load.
Please note that personal is only an option there if you are signed in
to a Google account, and that the new feature won't work yet for
Google Apps customers.
more info at ghacks site
I was searching for a way to get some information from chrome webstore (I have couple of extensions there) specifically feedbacks from users and user count. And I would like to do something with that data.
I searched about chrome web store API
but couldn't find anything.
found launchkit which does same thing, but for appStore
I am thinking there is no straight way to do it, but if anyone has done it or got some idea about it please share it along,
Thanks in advance
A simple google tells me there are already some possible helpful answers:
Get user feedbacks
How to get user feedback/bug reports on a Chrome Extension through itself?
Get user count
API call for user count in Chrome Web Store?
The closest I can find out is chromebeat and my extensions I would have to figure out how this works without an existing API and write my own after that I guess.
Recently Instagram changed their API's policy, which means you can no longer like/follow/unfollow using their API unless you are approved by Instagram to do so.
I own the website http://instapromobiz.com which uses JavaScript and PhP to automate likes/follows/unfollows using Instagram's API. This was doing great until Instagram made this update and I can no longer perform these actions.
My question is, is there any way to perform these actions without using Instagram's API? Sites like http://instagress.com are still working so there must be another way to perform these actions without using their API.
Does anybody have any suggestions that might point me in the right direction? Thanks in advance.
You should submit your app for review. They usually answer quickly.
Go to Manage Clients (https://www.instagram.com/developer/clients/manage/), then click on Edit button of your App. Your submission can be made over Permissions tab.
But, unfortunatelly, it's probably Instagram won't authorize an app that do like/ follow automatically. They want to ensure an authentic and consistent experience for the Instagram Community, so those actions should be manual. Good luck.
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.