Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GenericClient.forAuth ignores the project name set in the Auth instance #203

Open
andreavs opened this issue Jun 10, 2020 · 1 comment
Open

Comments

@andreavs
Copy link

Rather it uses the project name returned by the login call. This works fine for api key authorization, but when using a bearer token, it sets the project to root, which can be confusing.

@ngerstle-cognite
Copy link

The project the principal making the request belongs to isn't necessarily the project the request/requests should be made against.
As you've discovered, internal service principals (using a token from vault) have an identity in project 0, the root project, and have access to make requests in all other projects in the cluster (usually).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants