We are working on a project where we need to programmatically embed multiple Looker Studio reports into our web application for different users. However, many of our users do not have Google accounts, and we would like to avoid requiring them to sign in with Google to access the reports.
Our initial approach was to consider using a common service account that is not exposed to the users. This service account would authenticate with Looker Studio in the background and serve the reports seamlessly when users access our application. We want to ensure the process remains secure, and users will only see the reports they are authorized to view based on our app's authentication.
We have reviewed the available documentation but did not find a clear path to achieve this use case without requiring Google login. Specifically, we are looking for a way to:
We believe that having an option to support token-based authentication (e.g., JWTs or signed embedding) for Looker Studio reports would greatly benefit many teams looking to embed reports into their apps without relying on Google authentication for each user.
Could you please advise if there is a current solution or workaround for this use case? If not, we would appreciate it if this could be considered as a feature request for future updates.
Thank you for your attention, and I look forward to your response.