creamy-bear-51329
11/18/2024, 2:56 AMbrief-egg-61061
11/18/2024, 2:56 AMbrief-egg-61061
11/18/2024, 2:56 AMbest-plumber-65600
11/18/2024, 3:55 AMschema_id
on request to specify the desired schema ID doesnt works, always showing default_schema_id
, whats wrong?brief-egg-61061
11/18/2024, 3:55 AMbrief-egg-61061
11/18/2024, 3:55 AMschema_id
query parameter doesn't work as expected. Let me clarify the correct approach based on the available information. The issue you're experiencing is likely because the schema_id
cannot be specified directly as a query parameter in the registration flow initialization. Instead, the schema ID is typically set at the project level configuration. Here's what you need to know: 1. The default schema ID is usually set in the project configuration. This is referred to as default_schema_id
in the Ory configuration [as shown in this documentation](https://www.ory.sh/docs/guides/gitops#identity-schema). 2. To use a different schema for registration, you need to update your project's configuration to set the desired schema as the default, or create a new schema and set it as the default. 3. You can manage identity schemas through the Ory Console or by updating your project's configuration file if you're using GitOps workflow. To change the schema used for registration, you have a few options: 1. Update the default_schema_id
in your project configuration to point to the desired schema. 2. If you're using custom schemas, ensure they are properly added to your project configuration. For example: yaml schemas: - id: "your-custom-schema-id" url: "<https://storage.googleapis.com/your-custom-schema.json>"
Then set the default_schema_id
to your custom schema ID. 3. If you're using the Ory Network, you may need to update the schema through the Ory Console interface. Unfortunately, there isn't a straightforward way to specify a different schema ID per registration request as initially suggested. The schema used is determined by the project-level configuration. If you need to use multiple schemas dynamically, you might need to consider creating separate projects or implementing custom logic in your application to handle different registration flows based on your requirements. For more detailed information on managing identity schemas, you can refer to the [Ory documentation on managing identity schemas](https://www.ory.sh/docs/identities/model/manage-identity-schema#update-identities-to-use-a-new-schema). I apologize again for any confusion caused by my previous response. If you need further clarification or have more questions about managing schemas in Ory, please feel free to ask.