add Storm's OAuth to the list of pitfalls

This commit is contained in:
2024-08-15 23:12:29 -06:00
parent e0e7398efe
commit 8f85298aa5

View File

@ -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.