News for hackers. Stuff that matters.

ucarion

Re:NSA to Launch 'No Such Podcast,' on Wednesday September 04, 2024 @11:34AM (#41446983)
Anticipated audience: NOBUS
I don’t really have much an opinion on the what, I think I just know how I want this to feel. My preference is whatever works, and then making it obvious how it works. Mystery meat config files feel like the opposite, but I totally acknowledge that’s where you have to start when building this.
This is really cool. Is the "standards" thing basically some sort of LLM prompt? Like, do I just say in words "use slog, discourage logrus"?
Re:The non-Riemannian nature of perceptual color space on Friday August 02, 2024 @06:38PM (#41143269)
> Consequently, we need to adapt how we model color differences, as the current standard, ΔE, recognized by the International Commission for Weights and Measures, does not account for diminishing returns in color difference perception.

This isn't to reduce the notability of the article, but isn't BIPM's interest in any color-perception stuff basically limited to making lightbulbs roughly equally bright? (i.e. https://en.wikipedia.org/wiki/Luminous_efficiency_function) I guess I don't see how even nonlinearity in perceptual space matters for that purpose.

Yeah, we have this -- if you check out the docs for the endpoint where you accept a SAML login[1], there's an `attributes` (map<string, string>) that SSOReady returns to you. That contains the contents of the relevant SAML assertion's AttributeStatement.

So if you're familiar with Okta's parlance, both "Attribute Statements" and "Group Attribute Statements" are returned to you in `attributes`.

[1]: https://ssoready.com/docs/api-reference/saml/redeem-saml-acc...

The interface between your app and SSOReady is entirely over an HTTP API. We codegen SDKs for that HTTP API for Python and TypeScript, and will add more, but in the meantime the docs show you the curl you'd need to port:

https://ssoready.com/docs/api-reference/saml/redeem-saml-acc...

I think the reality is that the category of software we're open-sourcing isn't very big. We're gonna make our money doing other things, not all of which will be open-source.
My personal phone number and email is in the sidebar of app.ssoready.com for this exact reason.
> Question: For the free hosted SSO, how well are you going to be able to secure that, so that your customers aren't compromised through you?

Yeah, this is super important. No short answer here, it's just about doing the work and getting it right.

We're working with Oneleet for our SOC2 stuff (which we all know is largely theater) but also pretty thorough pentesting. I can email you their findings.

The reality is we're one of those companies that need to get this stuff right.

> Question: Will the free tier SSO have uptime guarantees, since it'll be a single point of failure for all your customers? For startups that decide they'd like it hosted for them, but need an SLA, do you expect to be able to provide that at a price doable by startups?

Our plan is to work out agreements on a case-by-case basis. It'd depend on exactly what you need. We take guarantees pretty seriously, so we're careful about what we promise.

We're not a services business. We don't want to make money off of "premium support". There is a modest price tag if you want an SLA.

> (Will a cloud provider pick up those customers using your software?)

Would you mind rephrasing?

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

OIDC2 is the better protocol, don't get me wrong. But lots of companies run on SAML, and it's the thing customers explicitly ask for.
Most folks will read that README and conclude SAML isn't going to happen for them today.

Take any language's biggest SAML implementation, and it's the same story of a library with some epic README covering dozens of public methods you may or may not need to use. People can't make heads or tails of this stuff.

Clarity and simplicity are the precursors to security. I'm pretty obsessed with making SAML clear and simple for folks.

Yeah SCIM is coming up. Auto-deprovisioning and stuff related to seat management are the big motivators I've seen.

Honestly IETF did a pretty good job with SCIM itself. It's not wacky in the way SAML is at all. In my experience the hardest part about integrating SCIM is setting up all the IDP-specific configuration around it. Like with SAML, it's a situation where Okta, Microsoft, OneLogin all have totally different terms for the exact same thing.

One thing I'm pretty excited about is that our SCIM support will also include a button where you can generate a setup link that you give to your customer. From that setup link they can self-serve configure their SAML+SCIM configuration.

We have that working for SAML right now, and it's nice because it means you don't need to write IDP-specific documentation walking customers through each product's weird terminology and quirky UI.

Launch HN: SSOReady (YC W24) – Making SAML SSO painless and open source

Hey everyone, I&#39;m Ulysse, CTO at SSOReady (https://github.com/ssoready/ssoready).SSOReady is an open-source (MIT) service that lets you implement SAML single sign-on without ever touching SAML yourself. You just need to implement two API endpoints: one to initiate SAML logins and another to receive incoming SAML messages. And then you&#39;re pretty much done.Here&#39;s me setting up SAML...

( Read More... | 98 comments | 136 points | on HN )
Re:A Gentle Introduction to SAML on Monday July 22, 2024 @06:14PM (#41040406)
It's hard to answer questions like this in the abstract. The details matter.
Re:A Gentle Introduction to SAML on Monday July 22, 2024 @05:43PM (#41040134)
Agreed. XML Signatures is the worst part of SAML. It's a spec that's basically begging to be done wrong. I remain confused as to what W3C were thinking.

https://ssoready.com/blog/engineering/xml-dsig-is-unfortunat...

Re:A Gentle Introduction to SAML on Monday July 22, 2024 @04:17PM (#41039341)
Is anyone going around choosing SAML today, though? XML fever has come and gone.

Usually SAML happens because customers ask for it, OIDC isn't as widely implemented by IDPs as SAML is, so you end up implementing SAML and moving on with life.

Re:US ICBM Launch Center Virtual Tour on Tuesday May 07, 2024 @12:31PM (#40287907)
The US has 400 land-based nuclear weapons, not thousands upon thousands. They're there to be a better thing for our enemies to aim at than our cities.
Re:The Stainless SDK Generator on Wednesday April 24, 2024 @02:51PM (#40148108)
Lots of these have been popping up lately, they all seem really good. This is the first one I've seen with an answer for "I want to customize the output by hand", which is neat.

https://buildwithfern.com/ https://liblab.com/ https://www.speakeasyapi.dev/

Between this and fancy API doc generators (Mintlify, etc.), I feel like we're finally getting close to being able to just go from OpenAPI to Stripe-level "polish".

I was in the last batch. The average is probably ~28 years old, but there are plenty of founding teams in their 40s and on. Plenty of folks with families. You wouldn't be a dinosaur.

Apply.

Re:Multi-Tenant Queues in Postgres on Thursday April 18, 2024 @09:02PM (#40082416)
Makes sense!

My gut tells me that it would often make sense to jump straight to shuffle sharding, where you'd converge on fair solutions dynamically, in a lot of cases. I'm looking forward to that follow-on article!

Re:Multi-Tenant Queues in Postgres on Thursday April 18, 2024 @04:21PM (#40080309)
This is pretty fancy stuff! Sorry if I'm just not reading carefully enough, but does this approach account for tenants whose messages take longer to process, as opposed to a tenant that sends a larger volume of messages?
Thanks! Yeah, we all stand on the shoulders of the giant that is Tailwind UI :)
Task management, lists/views, and general "journeys" management are all on the roadmap. There's a lot of stuff you need to do to be generally competent in this space, we're definitely launching very early here.

When I talked about Apex, I really mean the "scripting language that sees data mid-transaction" aspect of the language. Sounds like you're not really seeing the value there either? I totally agree that good old webhooks or some other trigger is seems almost always good enough if the API is fast.

Appreciate the suggestions re: comms and consent management. We're still not sure how we want to handle dialers.

Salesforce is where the money is. There's plenty of competitors.
Definitely going to add the hotkeys-for-objects feature! That's on my to-do list.

Want to work on reducing bundle sizes. Just haven't gotten a chance to get to that yet. Totally agree that load times really matter here, I've been focused on that and still have a few ways to speed that up.

Older »