Updated requirements for 1p sign in code testing

247 views
Skip to first unread message

Jochen Eisinger

unread,
Mar 4, 2021, 3:06:50 AM3/4/21
to chromium-dev, Chromium Embedders

Hey all,


I wanted to share some details about how we will manage the 1p APIs for signing into Chrome and Chrome OS going forward. Instead of relying on a quota for requests to those APIs, we’re asking you to join google-browser-si...@chromium.org with the accounts you will use for testing those APIs.


There won’t be additional restrictions at this time, i.e., for an account subscribed to this mailing list, you can sign in without additional quota on a chromium build as long as it has a valid OAuth 2.0 client id and secret (note that you can also set them via environment variables).


Accounts not on this mailing list won’t be able to sign in at all on chromium builds with OAuth 2.0 client ids and secrets soon after March 15.


Please note that this quota implementation can change at any point in the future.


best

-jochen


Jochen Eisinger

unread,
Apr 29, 2021, 4:53:09 AM4/29/21
to Gerd Röthig, Chromium Embedders
Hey,

no, there should be no such requirement. Simply hitting the join group button should be enough (assuming your signed in with the account you'd like to add to the group). Do you get any error messages or similar?

best
-jochen

On Thu, Apr 29, 2021 at 10:23 AM Gerd Röthig <gerd.r...@gmail.com> wrote:
Hello Jochen, hello all,

I have noted that for subscription to google-browser-signin-testaccounts, it is not enough to simply click "Join Group" as for other groups. You will have to send in a request for inclusion in the group to the group managers in addition.
As I did not find much more information:

Are there any formal conventions for that request, such as formatting conventions or required items of information to be provided?

Thank you very much for your help in advance and kind regards,

Gerd

Gerd Röthig

unread,
Apr 29, 2021, 4:15:19 PM4/29/21
to Chromium-dev, Jochen Eisinger, Chromium Embedders
Hello Jochen, hello all,

I have noted that for subscription to google-browser-signin-testaccounts, it is not enough to simply click "Join Group" as for other groups. You will have to send in a request for inclusion in the group to the group managers in addition.
As I did not find much more information:

Are there any formal conventions for that request, such as formatting conventions or required items of information to be provided?

Thank you very much for your help in advance and kind regards,

Gerd
Jochen Eisinger schrieb am Donnerstag, 4. März 2021 um 09:06:50 UTC+1:
Reply all
Reply to author
Forward
0 new messages