I want to point out that hacking a “run as” with a headless browser logged in as the user in a third-party service just to pretty print some pdf seems like a big security concern for a small return
I’m building a plugin that navigates to a page in the user’s Bubble app via a headless browser (which I’m running on AWS Lambda).
Access to the data in the underlying Bubble app will be managed via privacy rules.
Therefore, I want to effectively ‘run as the current user’ each time the headless browser is triggered and allow it to access the data that is appropriate for the user that triggered the action.
I was planning to:
Log the underlying users via an API Workflow and generate a Bearer …
I’m using Puppeteer to generate PDFs
Forum
Academy
Marketplace
Showcase
Pricing
Features