Is this plugin obsolete with the new organization feature?

[Vivek-Khamar]

• Do we still require this plugin to identify the idp with the email domain of the user ?

[sventorben]

Yes, the need for the Home IdP Discovery extension depends on your specific use case, as the organization feature does not yet fully replicate the extension's capabilities. Below is a breakdown of the differences between the organization feature and the extension:

1. What if you do not want to use organizations?

   • The extension does not require the use of organizations, offering a more lightweight approach. The organization feature, on the other hand, mandates configuring organizations, which may not align with your architecture or requirements.

2. What if multiple IdPs use the same domain names?

   • The extension handles such cases by letting users select thei IdP. The organization feature currently lacks this flexibility and assumes a 1:1 mapping between domains and organizations.

3. What if you do not want to use email but another attribute (e.g. UPN)?

   • The extension supports the use of alternative attributes like UPN (User Principal Name) for IdP identification. The organization feature is primarily designed around email domains, which may limit its usability in non-email scenarios.

It depends on your use case. The organization feature may work well for straightforward scenarios where email domain-based discovery suffices and organizations are part of your design. However, for advanced use cases - such as avoiding organizations, handling multiple IdPs with the same domain, or using non-email attributes for discovery - the extension is still required.