News for hackers. Stuff that matters.
Re:Launch HN: SSOReady (YC W24) – Making SAML SSO painless a... by bilalq on Tuesday July 30, 2024 @02:21PM (#41112432)
These days, I feel like this biggest obstacle with SAML is integrating with SaaS products. I've been in many situations where it requires back and forth emails to a support team. I've been handed a literal 204 page PDF on integrating with one vendor's SSO setup (the entire document was literally just for their SSO integration, nothing else). Attribute mappings are still a mess. It's wild how poor the experience still is.
Re:Launch HN: SSOReady (YC W24) – Making SAML SSO painless a... by ucarion on Tuesday July 30, 2024 @02:43PM (#41112736)
I've written one of these 204-page PDFs before (I think it was more like 20 pages though). The IDPs don't exactly make it easy on their customers to set this stuff up, and the burden ends up on the SP (i.e. you) to document to folks how to use their own IDP.

Incidentally we just shipped something for this. Rather than having to make a 204-page PDF, you can go into SSOReady, generate a setup URL, and give it to customers. Customers can visit that URL and they get a self-serve UI for configuring their SAML connection to your product.

https://ssoready.com/docs/idp-configuration/enabling-self-se...

Re:Launch HN: SSOReady (YC W24) – Making SAML SSO painless a... by mwcampbell on Tuesday July 30, 2024 @04:13PM (#41113657)
Wow. My company previously did an SSO implementation for our SaaS where we ran Shibboleth SP behind Apache just for SSO, with a little Python web app using mod_wsgi to call back to the main web app after SSO was completed. But for the customers that we've onboarded to SSO so far, we had to contract with a SAML expert to work with the customer to set it up. This self-service setup might be enough to make it worth our while to migrate to SSOReady.
Re:Launch HN: SSOReady (YC W24) – Making SAML SSO painless a... by crngefest on Wednesday July 31, 2024 @02:19AM (#41116793)
Sounds horrible, why would you use Shibboleth in $currentyear if you could just use OIDC?
Re:Launch HN: SSOReady (YC W24) – Making SAML SSO painless a... by havefunbesafe on Tuesday July 30, 2024 @02:23PM (#41112462)
OKTA does a pretty great job, if you want to spend $2X,XXX per year
Re:Launch HN: SSOReady (YC W24) – Making SAML SSO painless a... by bilalq on Tuesday July 30, 2024 @02:30PM (#41112549)
I'm referring to the opposite side of the problem. Even if you use Okta, if you want to integrate with company XYZ using SSO, no amount of Okta spend will save you.
Re:Launch HN: SSOReady (YC W24) – Making SAML SSO painless a... by rvnx on Tuesday July 30, 2024 @07:59PM (#41115263)
Supabase Auth ? https://supabase.com/docs/guides/auth/enterprise-sso/auth-ss...

Seems reasonably easy to use and a good platform to build a SaaS

Re:Launch HN: SSOReady (YC W24) – Making SAML SSO painless a... by SkyPuncher on Tuesday July 30, 2024 @05:07PM (#41114147)
SSO support took up well over 50% of our engineering teams customer support time.

One of the biggest challenges is our users tended to need to pull in a different department, that actually owned the SSO system. They had little incentive to hustle to get things to work, so there’s tickets would often drag on for ages.

We’d loom bad because we’d need certain information from our customer.