Need global api token support

[aravindsriraj]

Problem or use case

Glean CLI supports Oauth and client api token but doesn't support global api token. We are using global api token in our app , so that users can get personalized response from glean based on their work email. Currently we are restricted to client api token from a user and oauth is not suitable because our app runs in isolated sandbox

Proposed solution

Add support global api token authentication

Alternatives considered

No response

Additional context

No response

[rwjblue-glean]

In general, our view is that this CLI is more of a user space tool where it always operates as a single user (and 99% of the time via OAuth setup). That makes the mental model of developing on the tool a bit easier, as well as avoiding some gnarly bits around the sensitivity of global tokens (being able to impersonate ANY user is a very powerful thing -- and "with great power comes great responsibility" 😺 ).

In cases where a service is doing the kinds of things on behalf of another user, it's probably better to directly use the REST APIs (via our API Clients), which is what glean CLI is using under the hood anyways.

Can you help us understand the use case a bit more? Do you feel that glean CLI would be a better fit than using the REST API directly for your setup?