IdP v3 - Using multiple LDAP schemas

[Cantor, Scott]

> What is the best way to accomplish this requirement using IdP v3? Will we
> need to use two separate IdP installations, one for email and another for TVE
> users?

Even if you duplicated the Password flow, the flow definition uses the view name "login" to render the page, so there would be no way to separate it into a separate page, even if the back-end were configured differently. So you would have to basically copy and adapt the Password flow and adjust the flow definition slightly at this point. That should be corrected I think to make that more configurable, but there's no avoiding creating a second copy of the flow regardless, it's just not really designed to support that use case easily.

> Someone mentioned the new Spring authentication flows are complex and
> difficult to work with but that we may be able to accomplish it that way.

Well, hard or not, that's the basis of this version.

> But I don't have any idea of where to start looking for that option.

We have no significant development documentation, just some high level material. The code and existing flows are the only basis to work from. I don't have any kind of simple how-to to follow to make a copy of that flow, and even then, it's problematic, because we could break it in a new version since it's an implementation detail. So on balance, you're probably better off not doing this.

-- Scott