Hi all! 👋 Ory supports multiple identity schemas with different traits, but the self-service registration flow seems to only support the default schema. How can I implement two separate registration pages—one for users of schema A and another for users of schema B? Is there a way to specify which schema to use per registration flow? I know I can create identities via the Admin API, but in that case, I can’t set a password without hashing it myself, which adds complexity I’d like to avoid. Any ideas?

Hey, this is on the immediate roadmap and will make it into the next release and will be on ory network first. Can’t give exact times for ory network but likely this month even

great news! thank you 🙂

This is not a restriction, but used as a "hint" for rendering the correct form and inputs.

I see.. thanks for clarifying it.

Any user can also start a new flow with a different ID, so there is no point in restricting this.

I see what you mean. My thinking was: I have Page A and Page B — users of schemaA should log into Page A, and users of schemaB should log into Page B. So instead of allowing any user to log into Page A and then logging them out or showing an error, I thought this call could enforce that directly... but again I get your point, and any user could just change the param and force it.

It sounds like you should rather use two separate projects tbh

Ah, coming back to this...´ wouldn’t it be fine to have a single project with multiple user types? Essentially, UserA and UserB would just represent different global RBAC roles. for fine grained permissions I use keto