Dedicated Looker "Service" (API) Accounts

Looker Q&A Looker
, ,
1

Hi all, we have several dedicated Looker “service” accounts that are used to invoke the API for various purposes (LookML deployment automation, provisioning human users, etc). However, when I tried to create a new account recently I was unable to because the UI now asks for an email and won’t let you create an account without an email or with one that is being used by an existing user. Our existing service accounts all have the same email because they’re not real human users.

How can we create dedicated service type accounts if they must all have a different email address? Should I use a random dummy email (and tell it not to send the account invite). Or is the recommended practice to use the same user but generate multiple API keys? What about least privilege - they will all have the same permissions.

2

For us, we just create service accts users with fake emails. And if they all have same permissions, we put them in the same Group and assign the Role to the Group. Although if they all have same permissions i guess I don’t know why you’d need to create multiple service accounts.

3

I guess this question is no longer applicable now that Looker has first class support for service accounts.

1 Like
4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.