Multiple schemas/identities seem problematic

Hi there,

I want to start off by saying that the ecosystem which is being built is quite amazing, I am impressed! :slight_smile:

I came across some issue when spinning up kratos along with the oathkeeper proxy and selfservice-ui-node. I have defined multiple identity schemas in json. One is for an “employee” user type and the second one for a “customer” user type. My issue is that I would like to be able to specify the schema when registering a new account from the selfservice endpoints or public API or anywhere else where I can create a user. The admin API seems to offer a POST /identities which allows you to send schema_id in the request body which works, but there is no way to specify any credentials in this way. Also when I create a new user via the selfservice-ui-node and check the created identity in the admin API with GET /identities the schema_id always seems to be “default”, only when I use the previously mentioned admin API endpoint to create a user the schema is actually “employee” or “customer” instead of “default”.

So to sum up here are my main questions:
Is there any way to specify the schema_id to render the proper form inputs which belong to the specified schema?
Is there any way to get the actual schema_id on the entity of the identity when using the public GET /session/whoami enpoint instead of “default”?

I am using a docker-compose with the following images:

Let me know if any more details are needed, I will be happy to provide them.