I was worried a little writing my comment to Pattern for making Storybook and useAuth play nice?, as the association I created in my mind while reading that post was weaker than you expect.
Let me explain my thought: both RedwoodJS app integrated with Stripe and RedwoodJS app integrated with Storybook share the same problem - how to make them resolve the possible security conflicts. The situation I am describing in Redwood-Stripe integration - currently unresolved issues is particularly complicated because Stripe implements strongest possible security anywhere (because it handles financial transactions). This security takes over whenever any Stripe code gets invoked from the RW app. This does not mean that the RW app can just lean on Stripe and use Stripe’s security, because RW app needs to be able to protect its own code with authentication and authorization coverage (example: Login case).
RW Security implementation (see Security | RedwoodJS Docs)
currently does not handle this situation where two different security expectations co-exist.
Making sense?