Assigned
Status Update
No update yet.
Comments
ne...@sevco.io
The R8 build does include these files in our jar and they are not used/needed. I'll amend our build to avoid including them and merge it to the release branches.
ki...@oomnitza-dev.com
Project: r8
Branch: master
commit 80533c96c4561ab997f18ce65dd2c0c6a37a33b5
Author: Ian Zerny <zerny@google.com>
Date: Thu Jan 24 10:32:09 2019
Don't include kotlin module files in distribution.
Bug: 123310328
Change-Id: Ie70d4b15f08ffc0e7b754c558079002bd6a84334
M build.gradle
https://r8-review.googlesource.com/33381
Branch: master
commit 80533c96c4561ab997f18ce65dd2c0c6a37a33b5
Author: Ian Zerny <zerny@google.com>
Date: Thu Jan 24 10:32:09 2019
Don't include kotlin module files in distribution.
Bug: 123310328
Change-Id: Ie70d4b15f08ffc0e7b754c558079002bd6a84334
M build.gradle
sa...@oomnitza.com
Project: r8
Branch: d8-1.3
commit 73a2e504b0edd45eac64b6f242346b2793eae1fe
Author: Søren Gjesse <sgjesse@google.com>
Date: Fri Jan 25 09:23:25 2019
Version 1.3.54
Manually applied: Don't include kotlin module files in distribution.
CL:https://r8-review.googlesource.com/c/r8/+/33381
Bug: 123310328
Change-Id: Ifa5057f0c09d864295e200c287fb3d54cd3c79bf
M build.gradle
M src/main/java/com/android/tools/r8/Version.java
https://r8-review.googlesource.com/33485
Branch: d8-1.3
commit 73a2e504b0edd45eac64b6f242346b2793eae1fe
Author: Søren Gjesse <sgjesse@google.com>
Date: Fri Jan 25 09:23:25 2019
Version 1.3.54
Manually applied: Don't include kotlin module files in distribution.
CL:
Bug: 123310328
Change-Id: Ifa5057f0c09d864295e200c287fb3d54cd3c79bf
M build.gradle
M src/main/java/com/android/tools/r8/Version.java
ad...@vspartners.us
Project: r8
Branch: d8-1.4
commit 2fe3fcb0dc21ed70eb37cc74aae247deffc90d29
Author: Søren Gjesse <sgjesse@google.com>
Date: Fri Jan 25 09:12:36 2019
Version 1.4.30
Cherry-pick: Don't include kotlin module files in distribution.
CL:https://r8-review.googlesource.com/c/r8/+/33381
Bug: 123310328
Change-Id: I92dce45d6c031f2dd58780b0278a188142b21523
M build.gradle
M src/main/java/com/android/tools/r8/Version.java
https://r8-review.googlesource.com/33483
Branch: d8-1.4
commit 2fe3fcb0dc21ed70eb37cc74aae247deffc90d29
Author: Søren Gjesse <sgjesse@google.com>
Date: Fri Jan 25 09:12:36 2019
Version 1.4.30
Cherry-pick: Don't include kotlin module files in distribution.
CL:
Bug: 123310328
Change-Id: I92dce45d6c031f2dd58780b0278a188142b21523
M build.gradle
M src/main/java/com/android/tools/r8/Version.java
iv...@appsatori.eu
This change has landed in studio-3.3-dev and studio-3.4-dev. It has not yet landed in master, but will get there early next week when we do the weekly roll of R8 into studio.
de...@ollion.com
Fantastic!
an...@sraynercomputing.com
+1
me...@niharpatel.in
+1
sa...@listdevices.tpgprayoga.com
Hi,
Any updates on this? Do we need Cloud Identity Premium account to be able to add the scope? The google cloud API admin console does not seem to allow the addition ofhttps://www.googleapis.com/auth/cloud-identity.devices in the scope.
Any updates on this? Do we need Cloud Identity Premium account to be able to add the scope? The google cloud API admin console does not seem to allow the addition of
ju...@swappie.com
I just ran into this issue, and it is infuriating that there seems to be discrepancies between the documentation and what is actually doable.
I did get the API to work using Python and the methods described inhttps://cloud.google.com/identity/docs/how-to/setup-devices , but this is far from ideal, we would really want to call the API using normal Oauth methods from another service (or ideally apps script). Is the API still in beta or something?
I did get the API to work using Python and the methods described in
ka...@actindi.net
+1
ma...@khurram.dev
The authorization scope mentioned here https://cloud.google.com/identity/docs/reference/rest/v1/devices/list are different than the Oauth scopes mentioned here https://developers.google.com/identity/protocols/oauth2/scopes#cloudidentity . Everything is fine with Python implementation. But when I try to do it with Appscript then I am facing issues.
__
It seems that Devices Appscript class is also missing or not implemented so far.
__
It seems that Devices Appscript class is also missing or not implemented so far.
su...@google.com
su...@google.com
st...@gmail.com
Hi, Im a integration engineer and this issue is blocking me, is it posible to know if it is being fixed?
ji...@gmail.com
Hi can i check if there are any updates on this? Or did anyone found a way to call the api for the List Devices?
jp...@google.com
[Deleted User] <[Deleted User]>
I did some work around with java script for the above case and it is working. I hope this will help someone.
- Setup service account (
https://cloud.google.com/identity/docs/how-to/setup-devices )
- Provide access domain wide delegation to the service account (https://support.google.com/a/answer/162106 )
- Use googleapi to get access token using service account keys.
- Get the access token and use it in cloud devices api. (https://cloud.google.com/identity/docs/reference/rest/v1/devices/list )
const SCOPES = 'https://www.googleapis.com/auth/cloud-identity.devices ';
const BASE_URL = 'https://cloudidentity.googleapis.com/v1/ ';
// Change this to the location of the service account key
const SA_FILE = 'path/to/serviceaccount/keyfile/json';
// Enter the administrator to call as here.
const ADMIN_EMAIL = '';
function createDelegatedCredentials(userEmail) {
const credentials = require(SA_FILE);
const { google } = require('googleapis');
const jwtClient = new google.auth.JWT(
credentials.client_email,
null,
credentials.private_key,
[SCOPES],
userEmail
);
return jwtClient;
}
// AUTHENTICATE the service account and retrieve an oauth2 access token
async function getAccessToken() {
const jwtClient = createDelegatedCredentials(ADMIN_EMAIL);
try {
await jwtClient.authorize();
console.log('Access token: ' + jwtClient.credentials.access_token + '\n');
return jwtClient.credentials.access_token;
} catch (err) {
console.error('Error retrieving access token:', err);
process.exit(-1);
}
}
getAccessToken();
- Setup service account (
- Provide access domain wide delegation to the service account (
- Use googleapi to get access token using service account keys.
- Get the access token and use it in cloud devices api. (
const SCOPES = '
const BASE_URL = '
// Change this to the location of the service account key
const SA_FILE = 'path/to/serviceaccount/keyfile/json';
// Enter the administrator to call as here.
const ADMIN_EMAIL = '';
function createDelegatedCredentials(userEmail) {
const credentials = require(SA_FILE);
const { google } = require('googleapis');
const jwtClient = new google.auth.JWT(
credentials.client_email,
null,
credentials.private_key,
[SCOPES],
userEmail
);
return jwtClient;
}
// AUTHENTICATE the service account and retrieve an oauth2 access token
async function getAccessToken() {
const jwtClient = createDelegatedCredentials(ADMIN_EMAIL);
try {
await jwtClient.authorize();
console.log('Access token: ' + jwtClient.credentials.access_token + '\n');
return jwtClient.credentials.access_token;
} catch (err) {
console.error('Error retrieving access token:', err);
process.exit(-1);
}
}
getAccessToken();
Description
This will create a public issue which anybody can view and comment on.
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
We have a web application that we're trying to hook into the Cloud Identity Devices APIs (https://cloud.google.com/identity/docs/reference/rest/v1/devices/list ). The API requires the following scope: https://www.googleapis.com/auth/cloud-identity.devices.readonly .
When we attempt to authorize with that scope, we receive an error saying that the scope is invalid. The error is: Error 400: invalid_scope Some requested scopes cannot be shown: [https://www.googleapis.com/auth/cloud-identity.devices.readonly]
We have enabled Cloud Identity and added the scope to our application in the console.
What you expected to happen:
The authorization event should work as intended, resulting in thehttps://www.googleapis.com/auth/cloud-identity.devices.readonly scope being processed correctly. The following API call to Cloud Identity V1 Devices List should also work and return a list of devices.
Steps to reproduce:
Other information (workarounds you have tried, documentation consulted, etc):
We've tried the other Cloud Identity scopes listed on this page (https://developers.google.com/identity/protocols/oauth2/scopes ). They authorize correctly but the actual cloud identity V1 devices list call 403s because it's expecting the https://www.googleapis.com/auth/cloud-identity.devices.readonly scope.
We've also tried the other scopes individually listed on the List Devices V1 documentation page linked above. We would like to simply use the readonly scope but neither of the others resolve correctly.
It seems like thehttps://www.googleapis.com/auth/cloud-identity.devices.readonly scope doesn't exist in the same capacity to say https://www.googleapis.com/auth/cloud-identity.devices.lookup . If you navigate to both of those pages, the former 404s and the latter resolves to the lookup scope properly.