101–110 of 326 posts
Best to Auth0! I really hope you can maintain your company culture and excellence, but I can't risk my business on that now.
I hope this gives rise to another, smaller viable party outside of Amazon, Google, and Microsoft. Perhaps I'm jaded, perhaps hopelessly biased - but I can only see this as a net negative. Okta's open source packages receive a pitiful amount of attention (for example: https://github.com/okta/okta-oidc-js/issues?q=is%3Aissue+is%... ) with forks almost becoming a requirement. Auth0 by contrast has been "on the ball" for…
While I haven't interviewed with Auth0 it sounds like we both had the same experience and impression regarding Okta. You know something is off when your interview loop for an engineering role involves the President of Technology doing coding interviews and all your interviewers warn you about you about your upcoming interview with him. I thought it said a lot about the culture there.
> and integrated over time I'm reading too much into this sentence fragment and it fills me with fear. I smell breaking domain changes in the future. They can't allow the .auth0.com tenants to operate as-is forever, which means existing tenants will get grandfathered in and eventually forced off the .auth0.com domain onto okta's domains. I smell messy login sites in the future. I like Auth0's implementation of their…
So you're not fond of them? I have limited exposure. We use them at my place of work for 2fa for our VPN. And an organization we work with uses it for authentication. But I haven't had to use them in anything I've developed.
I'll make an exception for Office 365 / AAD when an organization has already got their userbase added, but after that I'd wager if an org is big enough to need their own federated authX, then they're big enough to deploy IdentityServer and be done with it.
Am I the only person left on earth that hasn't lost his mind?
Earlier quoted context omitted.
Except that AWS and Google have their own offerings (and the I think these aren't SSO companies as much as Auth as a Service providers)
Azure AD is the biggest in the game by far in terms of SSO, stretching every vertical from education to investment banking.
I hope this gives rise to another, smaller viable party outside of Amazon, Google, and Microsoft. Perhaps I'm jaded, perhaps hopelessly biased - but I can only see this as a net negative. Okta's open source packages receive a pitiful amount of attention (for example: https://github.com/okta/okta-oidc-js/issues?q=is%3Aissue+is%... ) with forks almost becoming a requirement. Auth0 by contrast has been "on the ball" for…
It's like Stripe for enterprise features, including SSO/SAML, Directory/SCIM, and more.
If anyone's looking for an Auth0 alternative, come check out FusionAuth! It's been built from the ground up for developer experience with a distinct lack of jargon, amazing customizability, an API first approach and great docs. Plus, enterprise features too, including SSO/SAML, OIDC, and more. https://fusionauth.io/docs/ (I work at FusionAuth.)
I hope this gives rise to another, smaller viable party outside of Amazon, Google, and Microsoft. Perhaps I'm jaded, perhaps hopelessly biased - but I can only see this as a net negative. Okta's open source packages receive a pitiful amount of attention (for example: https://github.com/okta/okta-oidc-js/issues?q=is%3Aissue+is%... ) with forks almost becoming a requirement. Auth0 by contrast has been "on the ball" for…
In the enterprise space, imo Microsoft is going to eat everyone’s lunch. Azure AD is pretty transformative, and their public facing stuff isn’t that far apart from what Okta does.