Switching off visibility of installed google apps marketplace app result in authorization failure in OAuth version 2 - google-oauth

In the older apps marketplace, a domain admin could switch off app visibility from the apps admin panel and the authentication/authorization to a 3rd party app still kept working.
After the OAuth2 migration, I see that switching off app visiblity to "Off", stops the 3rd party app to refresh the access tokens (for offline access) and returns access denied. Is this an issue or is it supposed to work this way ? We are using Service account to access.
I do not want the installed 3rd party app icon to appear in Gmail universal navaigation for all the domain users and still the autorization ( and offline acccess) to keep working.

I noticed this change as well. We have had to create multiple marketplace listings to get around this.
1 Listing for users that want the contextual gadget
1 Listing for those users that want the universal navigation
1 Listing for those users that want no universal navigation
You can turn off the universal navigation in the Marketplace Setup console by unchecking "Enable Universal Navigation extension"

Related

Actions on Google link third party service account using non-GoogleAssistant integration

I am working on Google Action for smart devices and using Dialogflow interaction schema with Java fulfillment. Fulfillment should call third party API to complete requests. For the purpose of the task, I must use a custom OAuth server. According to docs, I filled Action Account Linking information in Action Console with Grant Type: Authorization Code. For all intents including Welcome "Sign in required" is set.When testing with Google Home device or Google Home surface in Simulator menu, I get clear message "It looks like your Demo Service account is not linked yet. You can link Demo Service to your Google Account from the Google Home app." And as expected I get Linking Card in Google Home App to login and get AccessToken for third party service. Everything is OK here.
But when using Telegram integration or Phone surface in Simulator I just get "It looks like your Demo Service account is not linked yet" and nothing happen neither in Telegram, nor in Google Home App. How should user authentication for third party service be managed in this case?
Using the Actions on Google simulator, when you get the "It looks like your Demo Service account is not linked yet" you can achieve account linking by clicking on the DEBUG tab then open in a browser the url in "debugInfo". (See below)
The Phone surface simulates the Google Assistant app on Android or iOS devices. Users on these platforms will be prompted directly for account linking. (See below image)

Google games services rest sign in https redirect error

On my site I am using google play games services to sign in and I want to redirect to an https site but when I am signing in with https set as redirect url and click allow the sign in screen freezes.
Make sure you follow this steps that is stated in the Google Play Games documentation that to modify attributes related to your OAuth 2.0 client ID (web origins and redirect urls for a web app, bundle ID for an iOS app, etc.)
Open the Google Play Developer Console and navigate to your game.
On the Game Details page, scroll to the bottom and click the link to the linked Google Developers Console project.
In the Google Developers Console, select your project.
In the sidebar on the left, select APIs & auth. Make sure that the Google Play Games Services API status is ON in the displayed list of APIs.
In the sidebar on the left, select Registered apps.
Expand the OAuth 2.0 Client ID section and find the attribute to edit.
Also make sure you follow the steps in Creating Client IDs and Configure Service.

Google Drive Android Api reset Play Services Authorization

When debugging a GDAA app, I need to re-test a "brand new account" situation. I.e. getting the dialog that asks user to allow the Drive access:
"[YourApp] would like to: View and manage Google drive files that you
have opened or created by this app"
Is there a re-set method that would get me back to ground zero?
You can reset this via the Drive "manage apps" page on the web. Disconnect the app from your drive.
Have a look at the 'Google Settings' app on your device, in the 'Connected apps' section you should be able to select and disconnect your app. At least for other kinds of permissions (e.g. contacts), allowed apps show up there.
Edit: The same can be done via the web here.

Is it possible single Box App to authenticate different iOS apps?

The whole idea is to authenticate App, App Lite, App iPhone, App iPhone Lite with single Box.com App ID and return the user to the right app which redirected to the user to the authorization/authentication web site.
My Conclusion till now leads to using different App Id, because of lack of option to add different Redirect url's and respectively possibility for [box-api] to recognize the right caller application.
Will it work if I try to embed auth url in UIWebView and handle the response from that webView?
We currently don't support this use case, and you'll need separate App IDs

Is there a way to get the "remember me" checkbox work on Azure Mobile Service authentication for WinRT apps?

I'm trying to add Azure Mobile Service authentications to my WinRT app. I got everything working and I can sign in with all the 4 social media accounts(Facebook, Twitter, Google and Microsoft Account). But when I close the app and restart it, I have to write my user name and password even if I check the Remember Me button on either one of the options. Let say I logged in with my Facebook account, what I want to achive is, when I restart the app and click Login with Facebook, it shouldn't ask my username and password but automatically authenticate me. The remember me button seems to not working. Is there a way to achive this?
Thank you for the answers.
Edit: I'm using C#/XAML for my my app.
The following blog post covers caching the user's identity. http://www.thejoyofcode.com/Setting_the_auth_token_in_the_Mobile_Services_client_and_caching_the_user_rsquo_s_identity_Day_10_.aspx
According to this page: http://www.windowsazure.com/en-us/develop/mobile/tutorials/get-started-with-users-dotnet/
Note
... This method is easy to configure and supports multiple providers. However, this method also requires users to log-in every time your app starts. To instead use Live Connect to provide a single sign-on experience in your Windows Store app, see the topic Single sign-on for Windows Store apps by using Live Connect.