Yup, that was not clear. It was a typo and I've corrected it to $8K (this was for the domain). Thank you for pointing this out
The broker was $1-1.5K
428 karma · joined September 12, 2016
The broker was $1-1.5K
Yes, we do have outside contributions.
Over the long term, revenue will be from 1. hosting (as you mentioned), 2. Enterprises that pay for closed source features (regardless of whether they host with us or on their own infra)
Thats true.
For us this was about coupling authorization with an authentication system so that developers could have both with a single product.
During a check in, if there is a follow up question to dive deeper on, how does the flow for that work? I watched the demo video but wasnt able to catch it.
That way, you have as much control over it as if you built it yourself but it comes ready made and off the shelf.
The open source options are: Keycloak, SuperTokens, Ory and many more
(Im the cofounder of SuperTokens)
Seems like your other Java services were not an issue though?
Some recent feeedback:
"Hi yes, we are testing SuperTokens right now, and we are loving it Thanks for the great tool btw. it is really comfortable to integrate it into the project.
at first we decided to use Keycloak, spent a week to customize it for our needs. It was soooo painful :sweat_smile: then we started looking for alternatives"
"Been using it a bit for a pet project and I am quite impressed of how many integrations and documentation I find on its page. Also, really easy to use!" Just in case you are wondering where I found out about SuperTokens, it was on HackerNews"
I ask because Java in other large open source projects (Elastic Search, Cassandra, Android) and it really depends on how its being used (by Keycloak as well)
I've also come across GraalVM which can significantly reduce Java memory consumption (if that is something you are referring to)
If anyone has evaluated these / Keycloak, I'd be happy to have a discussion on it
Commercial open source companies (COSS) minimise those tradeoffs and give you the best of both worlds. That is - The power of build and the speed of buy.
You can migrate to and from a completely self hosted solution to a managed service as your needs change (for many COSS alternatives)
There is a lot of conversation here about building your own vs using something 'centralized'. All software comes with the “build vs buy” tradeoff.
Our goal at SuperTokens is to minimise those tradeoffs and give you the best of both worlds. That is - The power of build and the speed of buy.
You can migrate to and from a completely self hosted solution to a managed service as your needs change
SuperTokens is open source auth that is free and easy to setup. Our frontend UI is also far easier to customize
Check out SuperTokens.io too. We provide open source authentication as an alternative to SaaS provides such as Auth0 and Keycloak. Its free, writes to your own database (so you own your own data) and is built to be dead simple to setup.
Disclaimer: Cofounder of SuperTokens.io here. Would love to hear what you think
Yes, that is correct. Ideally, for the most secure setup, you should use the authorization code grant flow - which would involve your backend gaining access to Okta / Auth0 rather than your frontend. But yes, many people use the default setup which involves their own frontend having access to the user's info on the IdP. The default setup may also involve using localstorage with Auth0 (which we do not recommend - as do many other bodies such as OWASP and NIST).
Glad you liked our articles!
> In terms of implementing user management:
We provide the ability the following user management functions: - Loop through all users - Ban / unban via session revocation - Adding / modifying user roles to session and fetching them in a backend API (post session verification) and frontend
What we don't have: - A UI to manually see / edit the info mentioned above - Delete user functionality (we plan to add this)
So if you can do without the things we don't have, then it shouldn't take much time for you.
Feel free to join our Discord at supertokens.io/discord if you like!
We're the authors of the dzone article amongst others that you can find on our blog (supertokens.io/blog) on similar topics.
The reason Okta, Auth0 use OAuth 2.0 is because they are considered 3rd parties to your own backend. The user logins to Okta / Auth0 as the IdP and then they provide your app access to their backend to access the user's information.
With SuperTokens, the user is signing into your own backend as opposed to a 3rd party and hence OAuth is not required. Hope this answers your question!