Assigned
Status Update
Comments
or...@astrix-security.com <or...@astrix-security.com> #2
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.
ad...@kohavit.cloud <ad...@kohavit.cloud> #3
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
ad...@kohav.one <ad...@kohav.one> #4
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
jp...@google.com <jp...@google.com>
jp...@google.com <jp...@google.com>
la...@joyoushq.com <la...@joyoushq.com> #5
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
fo...@gmail.com <fo...@gmail.com> #6
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.
Description
A short description of the request:
Currently, user authentication is supported in a very limited way, in one 2 ways, both of which can't be used outside the domain the app is created in:
It would be extremely useful and convenient to be able to deploy my chat app using user authentication by granting it DWD, and to be able to impersonate any user in the domain, without having to be published in the Google Workspace marketplace.
In addition, using uesr authentication through DWD outside of the domain the app was created in would be useful for my use case, of deploying a chat app in a customer's environment, without making it available publicly.
What is the purpose of this new feature?
To support user authentication through domain-wide delegation of authority for the entire domain the app was created in without publishing on the Google Workspace marketplace, and to support user authentication through DWD for domains other than the one the chat app was created in.
What existing APIs would this affect?
The APIs that requires user authentication or that act differently when using user authentication to app authentication, e.g., spaces.setup and spaces.members.create .
Please provide any additional information below.
A pretty common use case for chat applications (in e.g., Slack, Microsoft Teams, and Google Chat) is to be installed in specific customers' environments and to able to send a Direct Message (DM) to all users in the domain, and to specific channels. Oftentimes in these cases, the developer of the app does not wish the app to be publicly available, and only installed in their respective customers' environments. Supporting such a use case would benefit many users of Google Workspace and Google Chat, and user authentication through domain-wide delegation of authority for the entire domain and outside the domain the app was created in seems like the perfect solution for this use case.