sophiabannet1
sophiabannet1 on Hacker News
Posted by
sophiabannet1 on Monday July 28, 2025 @03:19AM
from the ssojet.com dept.
Great post! The impersonation vs. delegation framing is spot on.
Even in enterprise SSO, proper delegation is clunky. We've toyed with OAuth 2.0 Token Exchange (RFC 8693), but support is patchy and confusing. An actor claim baked into tokens would add much-needed auditability.
Nice move by Supabase switching to asymmetric JWTs, eliminating the need to always call getUser() for verification should noticeably reduce latency at the edge; curious if anyone’s benchmarked how much faster auth.getClaims() actually is in practice compared to getUser()?
This is a cool idea, so many keyword tools feel unnecessarily gated these days. Love that this removes friction: no signup, instant results, and CSV export without paywalls sounds super useful, especially for quick research sessions or testing out early-stage content ideas.
We have reached a point where most B2B SaaS companies support SSO, but there is still a lot of confusion around which protocol to choose: SAML or OIDC. Both serve the same goal and allow users to authenticate using a trusted Identity Provider. We wrote a deep-dive comparison including when to use each, and gotchas to avoid.
Posted by
sophiabannet1 on Tuesday July 08, 2025 @01:59AM
from the ssojet.com dept.
Posted by
sophiabannet1 on Tuesday July 08, 2025 @01:48AM
from the self-post dept.
Just stumbled across something interesting: OWASP quietly released a new guide focused entirely on AI system testing. It's called the AI Testing Guide (AITG). Some of the stuff it digs into: Prompt injection and adversarial attacks, Privacy leaks from model outputs, Fairness, bias, and explainability testing, Data drift and real-world robustness and Model reproducibility.What I liked is it...
Posted by
sophiabannet1 on Friday June 27, 2025 @06:49AM
from the self-post dept.
I recently put together a deep-dive on the top Single Sign-On (SSO) providers for 2025. It is not just a list — we broke down key features like SAML/OIDC/SCIM support, pricing, use cases (startups vs enterprise), developer experience, and even included a checklist + questions to ask vendors.If you’re building a SaaS product or just exploring SSO options, this might save you a few hours of...
A reminder that even MFA isn’t foolproof—app-specific passwords can be a weak link. This attack shows how trust and timing, not tech, were the real weapons. Best to avoid ASPs and use OAuth or passkeys when possible. Big thanks to Google and Citizen Lab for sharing this.
because SSO is implemented using various protocols like SAML, OAuth 2.0, and OIDC, each with different use cases, data formats, and security models. Identity providers also have custom implementations, which lead to variations in endpoints, token formats, and user info structures, making a universal API flow difficult to standardize.
This is a fantastic breakdown of the real-world benefits of SSO—not just from the end-user perspective, but also from a developer and business standpoint. I especially appreciate the points about centralized user access control and reduced IT overhead, which are often overlooked when evaluating SSO adoption.
Excellent breakdown, this clearly illustrates why SSO is only half the story and PAM is essential for securing real privileged access.
A thought-provoking and realistic take on the evolving role of security engineers in the age of AI, versatility and orchestration are clearly the future.
A powerful reminder of why modern authentication must move beyond SMS—critical insights for anyone building secure systems today.
This is the funniest and most painfully accurate take on multi-factor authentication.
Totally agree, SaaS often shifts complexity rather than removing it, integrated platforms feel like coding with training wheels off.