3 ms·
> waste lots of time setting up OAuth-style login flows so the webapp can authenticate as the user Being real - if you can’t manage an oauth library in 2024, y
by maccard 2y ago
> waste lots of time setting up OAuth-style login flows so the webapp can authenticate as the user
Being real - if you can’t manage an oauth library in 2024, you probably shouldn’t be deploying these kinds of apps, it’s about 30 lines of code in go, JavaScript or c# , and they’re just the languages I’ve implemented it in.
- solatic 2y agoYou realize adding the library is like maybe 10% of the work? * Talk to IT and get your library added to SSO. Make sure both staging and prod. * Ensure user deprovisioning works when IT initiates. Prove to IT that the underlying cached tokens no longer work when the user is deprovisioned, even if it's really the upstream system's responsibility * Convince InfoSec that the particular OAuth library you chose is legit and doesn't pose a security risk If you think 90% of implementation isn't getting approvals internally then you clearly don't work for a big company.