From 8f85298aa57fbb4be399387bdde3194b4145b306 Mon Sep 17 00:00:00 2001
From: Mason Payne <mason@masonitestudios.com>
Date: Thu, 15 Aug 2024 23:12:29 -0600
Subject: [PATCH] add Storm's OAuth to the list of pitfalls

---
 Outline/Foundational answers.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Outline/Foundational answers.md b/Outline/Foundational answers.md
index 2a9b37c..9cd9395 100644
--- a/Outline/Foundational answers.md	
+++ b/Outline/Foundational answers.md	
@@ -15,6 +15,8 @@
      * Even the most technical enterprises needed hands on help to get SAML integrated correctly.
      * Underinvesting in development can prevent a polished outcome.
      * Need to keep up-to-date on security landscape changes. e.g. third party cookie rule changes, browser and mobile app behavior differences.
+   * Storm:
+     * Sometimes you don't need the added complexity of OAuth or other standards
    * Weave:
      * Third party auth providers will squeeze you once they know they have you.
      * Using a third party still requires you to have knowledge about all things authentication.