google-provisioning-api

Google App Engine and Group Provisioning

。_饼干妹妹 提交于 2020-01-07 02:33:07
问题 I really need some help here, I've been at this for almost 2 weeks. What I'm trying to do is use Google's provisioning API inside of GAE (Google App Engine) using oAuth2. I know there are a few of examples using oAuth1 to accomplish this. My understanding though is that oAuth1 is now deprecated and we must used oAuth2, please correct me if I am wrong. I've scoured the internet and the only example I could find to work from is this: http://gdata-samples.googlecode.com/svn-history/r232/trunk

Is it possible to access Provisioning API with service account?

…衆ロ難τιáo~ 提交于 2019-12-21 17:48:49
问题 My service account scopes are : https://apps-apis.google.com/a/feeds/user/ and DriveScope.DRIVE I authorized this same scope in "Manage third party OAuth Client access" in domain settings for my service account Id. I use the java client of the provisioning api. I build my credentials with the google oauth client with a GoogleCredential.Builder : credBuilder.setTransport(HTTP_TRANSPORT) .setJsonFactory(JSON_FACTORY) .setServiceAccountId(config.serviceAccountId)

How do you un-provision a device in order to set the Device Owner?

早过忘川 提交于 2019-12-20 03:56:08
问题 'm trying to set up Device Owner using the sample apps downloadable from developer.android.com https://developer.android.com/samples/NfcProvisioning/index.html https://developer.android.com/samples/DeviceOwner/index.html But when I NFC tap the devices in the logcat for the device I am trying to set the Device Owner for I see this: /? E/ManagedProvisioning﹕ Device already provisioned. However I am doing a factory reset just before attempting the provisioning, so how can I get the device into

Why are requests to the Provisioning, Profiles, Reporting, Reporting Visualization, Admin Audit, Email Migration (v1), or Documents List API failing?

╄→尐↘猪︶ㄣ 提交于 2019-12-17 17:17:00
问题 All of my calls to the following Google APIs have started failing: Provisioning Profiles Reporting Reporting Visualization Admin Audit Email Migration (v1) Documents List Has something changed? 回答1: All the API listed were shut down as of April 20, 2015 as per the deprecation policies of the Admin SDK and Documents List API. Please see the following migration guides for more information on how to migrate: Provisioning API to Admin SDK Directory API Profiles API to Admin SDK Directory API

Why are requests to the Provisioning, Profiles, Reporting, Reporting Visualization, Admin Audit, Email Migration (v1), or Documents List API failing?

大城市里の小女人 提交于 2019-12-12 06:15:41
问题 All of my calls to the following Google APIs have started failing: Provisioning Profiles Reporting Reporting Visualization Admin Audit Email Migration (v1) Documents List Has something changed? 回答1: All the API listed were shut down as of April 20, 2015 as per the deprecation policies of the Admin SDK and Documents List API. Please see the following migration guides for more information on how to migrate: Provisioning API to Admin SDK Directory API Profiles API to Admin SDK Directory API

Using Google Directory API to fetch all users in a domain

不羁的心 提交于 2019-12-11 19:26:15
问题 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

Python import gdata Google Apps Engine: Course Builder

拈花ヽ惹草 提交于 2019-12-08 13:34:30
问题 I'm working with Google Course Builder and I'm trying to import the GData library so that I can utilize the provisioning API to add members to google groups as they register for the course. Inside of utils.py of course builder lies the functions for registration. The problem is when I add import gdata.apps.groups.client and then run the server locally, the browser returns an internal server error 500. Obviously, I'm missing a step here, but where do I put the GData folder if not in my site

Get a list of users on a Google Apps domain

ぃ、小莉子 提交于 2019-12-08 08:35:02
问题 We have an app in the Google Apps Marketplace (the new one, i.e. using OAuth2) which needs to get a list of users in the domain. We're currently using the Provisioning API for this (which we know is deprecated, but there seems to be no better option). Lately however, we're starting to get "You are not authorized to access this API" 403's, for some domains. Does anyone know why we're suddendly getting 403's, a bug perhaps? There seem to be some other bugs as well, for example the scope https:/

Google Directory API 403 Insufficient Permission errors when requesting all account users

馋奶兔 提交于 2019-12-08 05:20:40
问题 I am trying to use the java Directory API to return a list of all the users in an account following the method outlined in the Google Documentation, however I consistently get 403 permission errors. Using the Java SDK my code looks like this, which 403 fails on the execute: Directory directory = new Directory.Builder(TRANSPORT, JSON_FACTORY, getCredential()).setApplicationName(PRODUCT_FULL_NAME).build(); Directory.Users.List list = directory.users().list(); list.setCustomer("my_customer");

Is it possible to access Provisioning API with service account?

…衆ロ難τιáo~ 提交于 2019-12-04 09:22:08
My service account scopes are : https://apps-apis.google.com/a/feeds/user/ and DriveScope.DRIVE I authorized this same scope in "Manage third party OAuth Client access" in domain settings for my service account Id. I use the java client of the provisioning api. I build my credentials with the google oauth client with a GoogleCredential.Builder : credBuilder.setTransport(HTTP_TRANSPORT) .setJsonFactory(JSON_FACTORY) .setServiceAccountId(config.serviceAccountId) .setServiceAccountPrivateKeyFromP12File(new File(config.keyFilePath)) .setServiceAccountScopes(SCOPES); .setServiceAccountUser("admin