<@U04UQ68083H> I have the same kratos identity con...
# ory-copilot
f
@chilly-king-10285 I have the same kratos identity config for my dev and staging environment, but the Ui nodes i get from ory are grouped as "default" in my dev environment and as "password" in staging config. How can I setup my identity config so that ui nodes are always grouped the same?
b
A message from kapa.ai
Based on the provided knowledge sources, there isn't enough specific information to directly answer why your UI nodes are grouped differently in dev and staging environments despite having the same Kratos identity configuration. However, I can provide some insights that might help you understand and potentially resolve the issue: 1. UI node grouping is determined by the authentication methods enabled and the flow type (login, registration, etc.). The groups typically include "default", "password", "oidc", and others depending on your configuration [Understanding UI nodes and error messages](https://www.ory.sh/docs/kratos/concepts/ui-user-interface#ui-node-groups). 2. The "default" group usually contains fields like the CSRF token, while the "password" group contains password-related fields [Login flow example](https://www.ory.sh/docs/kratos/bring-your-own-ui/custom-ui-basic-integration#get-login-flow). 3. To ensure consistent grouping, you should check: a. That both environments have the same authentication methods enabled. b. The flow type you're initiating is the same in both environments. c. Your Kratos configuration is indeed identical, particularly the
selfservice
and
identity
sections. 4. If you're using the Ory SDK or integrations, make sure you're using the same version and configuration in both environments [Login flow integration example](https://www.ory.sh/docs/kratos/bring-your-own-ui/custom-ui-basic-integration#create-login-flow). 5. When rendering your UI, you might want to consider filtering nodes by multiple groups to ensure you capture all relevant fields:
Copy code
javascript    filterNodesByGroups({      nodes: flow.ui.nodes,      groups: ["default", "password"],    }).map((node, idx) => mapUINode(node, idx))
This approach allows you to handle both grouping scenarios [Registration flow example](https://www.ory.sh/docs/kratos/bring-your-own-ui/custom-ui-basic-integration#create-registration-flow). If after checking these points you still see inconsistent grouping, you may want to compare the full UI node payloads from both environments to identify any differences. If the issue persists, it might be worth reaching out to Ory support or opening an issue on their GitHub repository for more specific guidance.