google-apps-marketplace

问题 I am running into a recurring issue with the Marketplace Listing/SDK. Anytime something minor is changed, the Contextual gadget disappears from the clients Gmail. When we look at the Marketplace App in the clients Google Apps Admin everything is fine. However if we go to "Data Access" and revoke permission and re-grant it, fairly soon the gadget will reappear. This has to be done for any customer that has the App installed. An example is fixing the issue described in the following link where

问题 When installing a Google Marketplace App, the flow usually ends with the admin in the app's settings on Google with the option to sign in now. Is there a way to end with the user actually using the app (i.e. not having to click the link to sign in to start using the app)? Could the user just be sent to the app on the optional setup without returning to the app settings page on Google without that causing other problems? Some of the documentation says: We strongly recommend that the

问题 Till very recently this feature was working where on app installation, the user was either presented an option to do the setup or automatically redirect the browser to the setup url. Now, it completely stopped working. Is anyone experiencing the same? If not, please let me know on how to debug this issue. Appreciate any help. 来源： https://stackoverflow.com/questions/21225585/google-app-marketplace-sdk-setup-url-stopped-working

问题 I am building an app for the Google Marketplace and just made the switch to OAuth 2.0 from 1.0 before final deployment. Before the switch, I was able to use the provisioning API to fetch users in a domain that has installed the app given, appropriate permissions have been granted. My experience with the Directory API (the OAuth 2 counterpart) requires that i perform a 2-legged OAuth to get an access token which I then uses to perform the Admin action. This only works if the access token

问题 We have successfully moved to the new Google Apps Marketplace using Omniauth2 etc. Yesterday our app got approved by Google. In our listing on the Marketplace the new Chrome Webstore Item Id is in place. But when I want to make any changes to the listing it says: "Vendor is not one of the owners of the current listing". The app still has the old Consumer Key, Application ID etc. From the documentation inserting the Chrome Web store ID should be sufficient. So basically we still have to app

问题 We've migrated our app from the old marketplace to the new one. After a few days we've received an email that we don't comply with an SSO policy - the user is not recognized after he installs the application. In the old app we had a specific setup link, that was opened for the user after he installed the app - thus making him recognizable. Is there such a function in the market? Is there some sort of a callback for the installation event in the new marketplace? P.S. the guy from Google told

问题 We want to use one of the Google API's Admin-SDK via OAuth2 access_token to get the Organization Name of the client who registers with our App from the Marketplace. The documentation says, all I need to do is query the below URL to get Organization Name http: // apps-apis.google.com/a/feeds/domain/2.0/{domainName}/general/organizationName And as expected, we have set https: // apps-apis.google.com/a/feeds/domain/ as one of scope parameter Can any one explain me how should I do this provided,

问题 We have a public market place app which we can install from the Chrome webstore . The "Integrate With Google" button is visible in the webstore. However when we try to put the same button in our website using <g:additnow applicationid="APP-ID"></g:additnow> We get a 403 Forbidden error from apis.google.com/additnow/additnow.html. I have verified that our app is public, app id is correct, even listed out website url in the clien id javascript origins. 回答1: As noted in the documentation, after

问题 We're trying to put our app on Google Marketplace, and one of the requirements was to use OAuth2 for authentication. Unfortunately (and strangely), AppEngine doesn't have an option for this. Right now, we are using OpenID for authentication. I've been trying to find resources online, but have failed in finding a definitive guide on how to do this properly. My concerns are: What scope should I use? How should sessions be managed? (the Users service handled this very well) What would the local

问题 I am in the process of upgrading my Marketplace applications to support the new marketplace api and OAUTH 2. I have managed to migrate most APIs but am stuck on the contacts api. With the the previous marketplace version we used 2LO and client key/client secret to authenticate across the Google Apps domain. My understanding is that the only way to do this in current version is with Service Accounts and OAuth 2. Based on the V3 calendar API I'm assuming something like this (although the