You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 3, 2022. It is now read-only.
In our org, for audit purposes data access must be associated with a human when it is not part of an automated process. While end-user creds work fine for some magics, the DataLab magics seem to reject these credentials and fall back on service account creds.
Using pydata-google-auth, within a GCP DataLab instance, I can replace non-Datalab magics with OAuth credentials:
In our org, for audit purposes data access must be associated with a human when it is not part of an automated process. While end-user creds work fine for some magics, the DataLab magics seem to reject these credentials and fall back on service account creds.
Using
pydata-google-auth
, within a GCP DataLab instance, I can replace non-Datalab magics with OAuth credentials:Yay, now my credentials are working for normal magics!
But replacing the datalab
Context
credentials doesn't stick:--> Access denied to service account
And the default credentials have been replaced back to a service account creds:
I understand that datalab expects service account credentials. Are user credentials completely unsupported?
The text was updated successfully, but these errors were encountered: