Closed gao-sun closed 10 months ago
@gao-sun any ETA here? this feat will convince me to integrate Logto into our platform to replace Auth0
@gao-sun any ETA here? this feat will convince me to integrate Logto into our platform to replace Auth0
@rannn505 thank you for your interest. we just reviewed the first version of the organization product design. we are now targeting late Oct this year.
btw, are you using Auth0's organization feature now? which part is most important to you? this will help us to have a better understanding on priorities.
@gao-sun Thank you for the update on the timeline. Yes, I am currently using Auth0's organization feature. The most crucial aspects for me are the ability to group users under an organizational entity and assign a domain for IdP-initiated login with SSO. These capabilities would sufficiently meet our needs. Looking forward to the late October release!
@rannn505 NP and thank you! The feature you describe is exactly on our roadmap. Looking forward to your feedback then.
Nice work @gao-sun! I am very excited to integrate Logto in our application, when this feature is available. You're right, I am looking for the organisation feature as described here, not for physically isolated tenants :)
@kswzr thank you! This feature will be available in Q4.
This is great!😃😃
@insulationman thank you for letting us know your expectation. let me know if i understand correctly, does it mean a username can have both password and federated sign-in for authentication? i.e. the following situation may exist:
@gao-sun any ETA here? this feat will convince me to integrate Logto into our platform to replace Auth0
@rannn505 thank you for your interest. we just reviewed the first version of the organization product design. we are now targeting late Oct this year.
btw, are you using Auth0's organization feature now? which part is most important to you? this will help us to have a better understanding on priorities.
@gao-sun How is it going?
@gao-sun Thank you for your reply. I would say that is correctly understood. An organization is set to use an enterprise connector or the default Logto identity provider, or maybe social (multiple connectors per org is rarely needed from my experience).
I would however say that just being able to group user into orgs and having some org metadata json field would cover most use cases to begin with. Just having this would have been great for me. The enterprise connection is requested by a few end users in my experience, but I work with small businesses.
thank you. we are working on this feature and it'll be released later this month
@gao-sun any ETA here? this feat will convince me to integrate Logto into our platform to replace Auth0
@rannn505 thank you for your interest. we just reviewed the first version of the organization product design. we are now targeting late Oct this year. btw, are you using Auth0's organization feature now? which part is most important to you? this will help us to have a better understanding on priorities.
@gao-sun How is it going?
we experienced some delay (you know software development :-) ), and here's the latest schedule:
the schedule is final, you can follow us on ProductHunt or subscribe to the newsletter to get notified once it's live.
update: there's a chance we'll deploy those features before the dates. i'll keep you posted!
Organizations feature has been official launched. Hence I'm closing the ticket.
Please check out our documentation for more details: https://docs.logto.io/docs/recipes/organizations/
What problem did you meet?
Finally we come to this far. These terms are confusing and even interchangeable between products.
For clarity, Organization and Tenant are two different things in Logto. Both of them have a precise definition, please see CIAM 101: Authentication, Identity, SSO for details.
In short:
You can see a lot of SaaS providers are using the Organization model for managing their users.
Describe what you'd like Logto to have
Support Organization.
Related issue
3603