Davide Walder

> Hei @DavideWalder > > I think we do have some problems with what validate and verified means and what the impact of the property validate org domains has. >...

@hifabienne I see, having the option as you suggested would make sense, thanks! Feel free to close the issue

Thanks for the explanation, this might be difficult since we need to be able to have multiple customers each with their own IDP that can't be shown to the others....

@hifabienne Both cases: - the user doesn't exist yet (will be created on the first login with its organization's IDP) - the user already exists (and might want to link...

The flow could be: - the user is presented with the login page of the instance - the user enters its email address - discovery: - if the domain of...

> I created an issue to track this new feature: #4463 > > @DavideWalder In terms of urgency what does that mean in a timeline? When would you need this...

Another question related to domain discovery: Currently, for users from customers with unique domains, I can create a username from the local part of their email address and register the...

> > Another question related to domain discovery: > > Currently, for users from customers with unique domains, I can create a username from the local part of their email...

@hifabienne Regarding the unique organization holding all the users, this might be a viable option. I would then only create users in separate organizations when dealing with SSO, different IDPs...

> @DavideWalder > > I am not sure how your complete usecase looks like. There might be solutions. But without understanding the use case it is difficult to help. >...