Live data from Hacker News

AWS Single Sign-On

aws.amazon.com

41–50 of 119 posts

Re: AWS Single Sign-On

#41

Wonder if and when we’ll see decent Excel/Word replacements from Amazon, perhaps coupled with a thin Linux distro. At that point you’d be able to completely do away with Microsoft in many organisations, and Amazon could simply gobble up those dollars. They’ve got enough money they could make it work.

They have Amazon WorkDocs and Amazon WorkMail. I've never seen them in the wild though...

Re: AWS Single Sign-On

#42
post #40
post #34

Earlier quoted context omitted.

Out of curiosity (and ignorance), why SAML vs JWT or some less awful protocol?

JWT is also an awful protocol, and it's also not an SSO standard. There's still time for us not to bet the farm on JWT, and I urge clients to avoid it.

Just Say No to JWT

Re: AWS Single Sign-On

#43
post #25

Earlier quoted context omitted.

You might want to double check those facts. There are probably billions of SAML users. Any significant O365 implementation is using SAML. Any SaaS that allows enterprise login is using SAML. If you do business with Spectrum, you are using SAML when you login. If you interact with most government agencies, you are using SAML. That’s not to say that it does not have risk, but adoption is not an issue!

Chase Bank is another one, off the top of my head. SAML is huge. I have no idea where the guy above us is getting is intel.

Each of the largest 10 banks in the US use SAML identity providers for their SSO.

Re: AWS Single Sign-On

#44
post #40
post #34

Earlier quoted context omitted.

Out of curiosity (and ignorance), why SAML vs JWT or some less awful protocol?

JWT is also an awful protocol, and it's also not an SSO standard. There's still time for us not to bet the farm on JWT, and I urge clients to avoid it.

Why not OIDC? (which is a SSO standard)

Re: AWS Single Sign-On

#45
post #40

Earlier quoted context omitted.

JWT is also an awful protocol, and it's also not an SSO standard. There's still time for us not to bet the farm on JWT, and I urge clients to avoid it.

Why not OIDC? (which is a SSO standard)

OpenID Connect is significantly less popular, especially among enterprise on-site apps, than SAML.

Re: AWS Single Sign-On

#46
post #29

If this is interesting to you but you're iffy about setting up another directory service or having AWS be your central list of identities for all your apps, we're open sourcing The Identity Mutilator, a Golang SAML IdP, in a couple weeks. It's self-contained (for now) so doesn't depend on AD or LDAP --- just Postgres --- and runs just fine in a tiny Docker container.

In your own words, you're a SAML IdP, not an SSO manger, like AWS SSO. I believe you're more akin to AWS Cognito than to AWS SSO. Unless I'm missing something in your description

Re: AWS Single Sign-On

#49

Wonder if and when we’ll see decent Excel/Word replacements from Amazon, perhaps coupled with a thin Linux distro. At that point you’d be able to completely do away with Microsoft in many organisations, and Amazon could simply gobble up those dollars. They’ve got enough money they could make it work.

Excel needs to go, better wait for it to fade, it is not a modern data analytics system, not at all.

It isn't. But what do you replace it with? Better solutions are likely to only cover a fraction of use cases, so they really need to be stellar to win over users.

Re: AWS Single Sign-On

#50
post #11

Earlier quoted context omitted.

$288 comes from here: https://aws.amazon.com/directoryservice/pricing/ It looks like AD Connector is much less: https://aws.amazon.com/directoryservice/other-directories-pr...

I think you're looking at the Enterprise domain controller pricing. the Standard size (up to 30,000 objects) is 12 cents/hour for two controllers. $0.12 * 24 * 30 = $86.40/month.

You're right! Thanks for the pick-up.

I'd change the statement in my parent post, but I don't seem to be able to edit it.

Post reply on HN