The following article outlines changes to google oauth for webviews, https://developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html?m=1
"In the coming months, we will no longer allow OAuth requests to Google in embedded browsers known as 'web-views'".
Will there by any changes to google oauth support in the JavaFX WebView? https://docs.oracle.com/javase/8/javafx/api/javafx/scene/web/WebView.html
Related
my dev and I would like to implement the google picker on our website. It will allow the web-visitor to upload their files from their Google drive to our website.
My dev is now trying to get the API for the google picker however they are asking for a "demo video that showcases the process to request an OAuth token" and we were wondering how we should do it when we don't have the API from google.
We are doing all of this on the staging site and we were wondering how are we suppose to do this demo video when the API is not provided and not installed.
please enlighten us, thank you!
See the question How can I make sure the verification process is as streamlined as possible? in the FAQ. It explains what the verification team is looking for with the video. Mostly it's just about showing how your product uses OAuth and the various APIs -- in your case how it asks for access to Drive, how the picker is used, etc. You're showing the integration from the user perspective.
The Google One-Tap Sign-Up documentation web page displays the following message:
This API is currently in closed beta. We are improving the API's cross-browser functionality and will provide updates here in the coming months.
https://developers.google.com/identity/one-tap/web/
Is One-Tap Sign-Up safe for production use currently?
Also while testing the functionality I was not able to test this on non-Chrome browsers successfully. Is this available for browsers other than Chrome?
was also looking for a clear answer to this
from troubleshooting page:
...If you see the warning The client origin is not permitted to use this API, your service has not yet been accepted to the beta. New sign-ups to this beta are currently closed.
They also have a supported browser \ os table on there
google said they will no longer allow OAuth requests to Google in embedded browsers known as “web-views. actually starting 20 April 2017.
I work for LGE.
LG has been using android and ios webView in many services.
Changing it to android and ios sdk makes so many trouble in our company.
Dose anyone knows about this solution?
Is there any way to use webview countinuingly?
And..
Google said they will start blocking OAuth requests using web-views for all OAuth clients on platforms where viable alternatives exist.
LG smart TV uses WebOs platform, so there is no alternatives exists except for
using webviews.
how can we request exception for webos platforms?
Looking at this site http://www.thefancy.com/ and clicking the Sign up button followed by the Twitter option it brings up a window for Twitter Login.
I assume this is the JS approach to Twitter login in a similar fashion to Facebooks.
On my site I have already implemented Connect With Facebook (using JS) and to keep my site consistent I would like to know how to do this using Twitter's Sign On service.
Does anyone have any useful advice or links to help me with this - I can only find guides that take the user to Twitter's website during login and then back again to mine which is not what I want.
Many thanks
EDIT:
I did notice this on Twitter's site:
"Reminder: It is strongly discouraged to use OAuth 1.0A with client-side Javascript."
Why do Twitter recommend against using JS with OAuth while Facebook and Google are happy to go with it?
tHave you looked into Twitter OAuth? In order for Twitter to grand your site details, it has to redirect your users momentarily to twitter for them to verify this access. This link explains it a bit better: https://developer.twitter.com/en/docs/basics/authentication/overview/3-legged-oauth
Temboo simplifies the process of developing Twitter sign up (via OAuth). See here for details: https://live.temboo.com/library/Library/Twitter/OAuth/
Temboo doesn't have a JS library though, so you will have to use the REST API.
Full disclosure: I work at Temboo.
I'm working on redesigning an older site and I'm upgrading it to HTML5. The site currently has both Google and Yahoo site verification META tags.
I'm using HTML5 Reset as a starting template and it only has an area for Google site verification, not Yahoo. Also, the W3C Validator validates Google site verification in HTML5, but not Yahoo.
Does anyone have an opinion as to whether or not Yahoo site verification is important or useful? And does it hold any weight with SEO these days?
No.
Yahoo search is now powered by Bing.
You can remove both (Google and Bing) verification references and authenticate using other methods (DNS is best). Bing only offers meta tag and XML methods.